Extension Codeは安全ですか?

Extension Code — Nerq Trust Score 63.8/100 (Cグレード). 1つの信頼次元の分析に基づき、概ね安全だがいくつかの懸念があると評価されています。 最終更新:2026-04-05。

Extension Codeは注意して使用してください。 Extension Code はsoftware toolです (code extension for tiptap) Nerq信頼スコア63.8/100(C), 3つの独立したデータ次元に基づく. Nerq認証閾値未満 データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. 最終更新: 2026-04-05. 機械可読データ(JSON).

Extension Codeは安全ですか?

CAUTION — Extension Code has a Nerq Trust Score of 63.8/100 (C). 中程度の信頼シグナルがありますが、一部懸念される領域があります that warrant attention. Suitable for development use — review セキュリティ and メンテナンス signals before production deployment.

セキュリティ分析 → プライバシーレポート →

Extension Codeの信頼スコアは?

Extension CodeのNerq信頼スコアは63.8/100で、Cグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む1の独立した次元に基づいています。

Compliance
100

Extension Codeの主なセキュリティ調査結果は?

Extension Codeの最も強いシグナルはコンプライアンスで100/100です。 既知の脆弱性は検出されていません。 Nerq認証閾値70+にまだ達していません。

Compliance: 100/100 — covers 52 of 52 jurisdictions

Extension Codeとは何で、誰が管理していますか?

作者GitHub Actions
カテゴリUncategorized
Sourcehttps://www.npmjs.com/package/@tiptap/extension-code

規制コンプライアンス

EU AI Act Risk ClassNot assessed
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

Extension Codeの他プラットフォーム

他のレジストリでの同じ開発者/企業:

@nuxtjs/color-mode
76/100 · npm
@nomicfoundation/hardhat-zod-utils
74/100 · npm
@nomicfoundation/slang
72/100 · npm
@nomicfoundation/hardhat-viem-assertions
70/100 · npm
@nomicfoundation/hardhat-mocha
70/100 · npm

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 セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.

How Nerq Assesses Extension Code's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 次元. Here is how Extension Code performs in each:

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:

Risk guidance: Extension Code is suitable for development and testing environments. Before production deployment, conduct a thorough review of its セキュリティ 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:

  1. Check the source code — 確認してください repository セキュリティ policy, open issues, and recent commits for signs of active メンテナンス.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Extension Code's dependency tree.
  3. レビュー permissions — Understand what access Extension Code requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Extension Code in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=@tiptap/extension-code
  6. 確認してください 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.
  7. 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 セキュリティ 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:

Data handling

Understand how Extension Code processes, stores, and transmits your data. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency セキュリティ

Check Extension Code's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.

Update frequency

Regularly check for updates to Extension Code. セキュリティ patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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.

License and IP コンプライアンス

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:

Conduct regular audits

Periodically review how Extension Code is used in your workflow. Check for unexpected behavior, permissions drift, and コンプライアンス with your セキュリティ policies.

Keep dependencies updated

Ensure Extension Code and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.

Follow least privilege

Grant Extension Code only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for セキュリティ advisories

Subscribe to Extension Code's セキュリティ advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

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:

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 セキュリティ 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 次元.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks 中程度 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 メンテナンス 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 セキュリティ and quality. Conversely, a downward trend may signal reduced メンテナンス, 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 — セキュリティ, メンテナンス, ドキュメント, コンプライアンス, and community — has evolved independently, providing granular visibility into which aspects of Extension Code are strengthening or weakening over time.

重要なポイント

よくある質問

Extension Codeは安全ですか?
注意して使用してください。 @tiptap/extension-code Nerq信頼スコア63.8/100(C). 最も強いシグナル: コンプライアンス (100/100). スコアの基準: multiple trust 次元.
Extension Codeの信頼スコアは?
@tiptap/extension-code: 63.8/100 (C). スコアの基準: multiple trust 次元. Compliance: 100/100. 新しいデータが利用可能になるとスコアが更新さ���ます. API: GET nerq.ai/v1/preflight?target=@tiptap/extension-code
Extension Codeのより安全な代替は何ですか?
In the Uncategorized category, more software tools are being analyzed — 後で確認してください. @tiptap/extension-code scores 63.8/100.
Extension Codeの安全性スコアはどのくらいの頻度で更新されますか?
Nerq continuously monitors Extension Code and updates its trust score as new data becomes available. データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. Current: 63.8/100 (C), last 認証済み 2026-04-05. API: GET nerq.ai/v1/preflight?target=@tiptap/extension-code
規制環境でExtension Codeを使用できますか?
Extension Code has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

関連項目

Disclaimer: Nerqの信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。

分析とキャッシュにCookieを使用しています。 プライバシー