Czy Extension Code jest bezpieczny?
Extension Code — Nerq Trust Score 63.8/100 (Ocena C). Na podstawie analizy 1 wymiarów zaufania, jest ogólnie bezpieczny, ale z pewnymi zastrzeżeniami. Ostatnia aktualizacja: 2026-04-06.
Używaj Extension Code z ostrożnością. Extension Code to software tool (code extension for tiptap) z wynikiem zaufania Nerq 63.8/100 (C), based on 3 niezależnych wymiarów danych. Poniżej zweryfikowanego progu Nerq Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: 2026-04-06. Dane odczytywalne maszynowo (JSON).
Czy Extension Code jest bezpieczny?
CAUTION — Extension Code has a Nerq Trust Score of 63.8/100 (C). Ma umiarkowane sygnały zaufania, ale wykazuje pewne obszary budzące obawy that warrant attention. Suitable for development use — review bezpieczeństwo and konserwacja signals before production deployment.
Jaki jest wynik zaufania Extension Code?
Extension Code ma Nerq Trust Score 63.8/100 z oceną C. Ten wynik opiera się na 1 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.
Jakie są kluczowe ustalenia bezpieczeństwa dla Extension Code?
Najsilniejszy sygnał Extension Code to zgodność na poziomie 100/100. Nie wykryto znanych luk w zabezpieczeniach. It has not yet reached the Nerq Verified threshold of 70+.
Czym jest Extension Code i kto go utrzymuje?
| Autor | GitHub Actions |
| Kategoria | Uncategorized |
| Źródło | https://www.npmjs.com/package/@tiptap/extension-code |
Zgodność z przepisami
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Extension Code na innych platformach
Ten sam deweloper/firma w innych rejestrach:
What Is Extension Code?
Extension Code is a software tool in the uncategorized category: code extension for tiptap. Nerq Trust Score: 64/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.
How Nerq Assesses Extension Code's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Extension Code performs in each:
- Compliance (100/100): Extension Code is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
The overall Trust Score of 63.8/100 (C) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.
Who Should Use Extension Code?
Extension Code is designed for:
- Developers and teams working with uncategorized tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Extension Code is suitable for development and testing environments. Before production deployment, conduct a thorough review of its bezpieczeństwo posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Extension Code's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Sprawdź repository bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Extension Code's dependency tree. - Opinia permissions — Understand what access Extension Code requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Extension Code in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=@tiptap/extension-code - Sprawdź license — Confirm that Extension Code's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
- Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses bezpieczeństwo concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Extension Code
When evaluating whether Extension Code is safe, consider these category-specific risks:
Understand how Extension Code processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Extension Code's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.
Regularly check for updates to Extension Code. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.
If Extension Code connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.
Verify that Extension Code's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Extension Code in violation of its license can expose your organization to legal liability.
Best Practices for Using Extension Code Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Extension Code while minimizing risk:
Periodically review how Extension Code is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.
Ensure Extension Code and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.
Grant Extension Code only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Extension Code's bezpieczeństwo advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Extension Code is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Extension Code?
Even promising tools aren't right for every situation. Consider avoiding Extension Code in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional zgodność review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Extension Code's trust score of 63.8/100 meets your organization's risk tolerance. We recommend running a manual bezpieczeństwo assessment alongside the automated Nerq score.
How Extension Code Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Extension Code's score of 63.8/100 is above the category average of 62/100.
This positions Extension Code favorably among uncategorized tools. While it outperforms the average, there is still room for improvement in certain trust wymiarów.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks umiarkowany in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.
Trust Score History
Nerq continuously monitors Extension Code and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or konserwacja patterns change, Extension Code's score is updated within 24 hours.
Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, growing technical debt, or unresolved vulnerabilities. To track Extension Code's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=@tiptap/extension-code&include=history
Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Extension Code are strengthening or weakening over time.
Kluczowe wnioski
- Extension Code has a Trust Score of 63.8/100 (C) and is not yet Nerq Verified.
- Extension Code shows umiarkowany trust signals. Conduct thorough due diligence before deploying to production environments.
- Among uncategorized tools, Extension Code scores above the category average of 62/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Często zadawane pytania
Czy Extension Code jest bezpieczny?
Jaki jest wynik zaufania Extension Code?
What are safer alternatives to Extension Code?
How often is Extension Code's safety score updated?
Can I use Extension Code in a regulated environment?
Zobacz także
Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.