¿Es Extension Code Seguro?
Extension Code — Nerq Trust Score 63.8/100 (Grado C). Basado en el análisis de 1 dimensiones de confianza, se considera generalmente seguro pero con algunas preocupaciones. Última actualización: 2026-04-05.
Usa Extension Code con precaución. Extension Code es un software tool (code extension for tiptap) con un Nerq Trust Score de 63.8/100 (C), basado en 3 dimensiones de datos independientes. Por debajo del umbral verificado de Nerq Datos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Última actualización: 2026-04-05. Datos legibles por máquina (JSON).
¿Es Extension Code Seguro?
CAUTION — Extension Code has a Nerq Trust Score of 63.8/100 (C). Tiene señales de confianza moderadas pero muestra algunas áreas de preocupación that warrant attention. Suitable for development use — review seguridad and mantenimiento signals before production deployment.
¿Cuál es la puntuación de confianza de Extension Code?
Extension Code tiene una Puntuación de Confianza Nerq de 63.8/100, obteniendo un grado C. Esta puntuación se basa en 1 dimensiones medidas independientemente.
¿Cuáles son los hallazgos de seguridad clave de Extension Code?
La señal más fuerte de Extension Code es cumplimiento con 100/100. No se han detectado vulnerabilidades conocidas. Aún no ha alcanzado el umbral verificado de Nerq de 70+.
¿Qué es Extension Code y quién lo mantiene?
| Autor | GitHub Actions |
| Categoría | Uncategorized |
| Fuente | https://www.npmjs.com/package/@tiptap/extension-code |
Cumplimiento Regulatorio
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Extension Code en Otras Plataformas
Mismo desarrollador/empresa en otros registros:
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 seguridad vulnerabilities, mantenimiento activity, license cumplimiento, and adopción por la comunidad.
How Nerq Assesses Extension Code's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiones. 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 seguridad 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 — Revisar el/la repository seguridad policy, open issues, and recent commits for signs of active mantenimiento.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Extension Code's dependency tree. - Reseña 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 - Revisar el/la 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 seguridad 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. Revisar el/la 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 seguridad risk.
Regularly check for updates to Extension Code. Seguridad 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 cumplimiento with your seguridad policies.
Ensure Extension Code and all its dependencies are running the latest stable versions to benefit from seguridad patches.
Grant Extension Code only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Extension Code's seguridad 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 cumplimiento 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 seguridad 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 dimensiones.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderado 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 mantenimiento 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 seguridad and quality. Conversely, a downward trend may signal reduced mantenimiento, 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 — seguridad, mantenimiento, documentación, cumplimiento, and community — has evolved independently, providing granular visibility into which aspects of Extension Code are strengthening or weakening over time.
Puntos Clave
- Extension Code has a Trust Score of 63.8/100 (C) and is not yet Nerq Verified.
- Extension Code shows moderado 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.
Preguntas Frecuentes
¿Es Extension Code Seguro?
¿Cuál es la puntuación de confianza de 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?
Ver también
Disclaimer: Las puntuaciones de confianza de Nerq son evaluaciones automatizadas basadas en señales disponibles públicamente. No son respaldos ni garantías. Siempre realice su propia diligencia debida.