Devhelm Demoは安全ですか?

Devhelm Demo — Nerq Trust Score 42.5/100 (Eグレード). 3つの信頼次元の分析に基づき、顕著なセキュリティ上の懸念があると評価されています。 最終更新:2026-04-08。

Devhelm Demoには注意が必要です。 Devhelm Demo はsoftware toolです Nerq信頼スコア42.5/100(E), 3つの独立したデータ次元に基づく. Nerq認証閾値未満 メンテナンス: 0/100. 人気度: 0/100. データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. 最終更新: 2026-04-08. 機械可読データ(JSON).

Devhelm Demoは安全ですか?

NO — USE WITH CAUTION — Devhelm Demo has a Nerq Trust Score of 42.5/100 (E). 平均以下の信頼シグナルで、重大なギャップがあります in セキュリティ, メンテナンス, or ドキュメント. Not recommended for production use without thorough manual review and additional セキュリティ measures.

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

Devhelm Demoの信頼スコアは?

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

メンテナンス
0
ドキュメント
0
人気度
0

Devhelm Demoの主なセキュリティ調査結果は?

Devhelm Demoの最も強いシグナルはメンテナンスで0/100です。 既知の脆弱性は検出されていません。 Nerq認証閾値70+にまだ達していません。

メンテナンス: 0/100 — メンテナンス活動が低い
ドキュメント: 0/100 — 限定的な文書化
人気度: 0/100 — 1 スター( pulsemcp

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

作者https://github.com/devhelmhq/devhelm-mcp
カテゴリインフラストラクチャ
Stars1
Sourcehttps://github.com/devhelmhq/devhelm-mcp
Protocolsmcp

infrastructureの人気の代替品

n8n-io/n8n
78.5/100 · B
github
langflow-ai/langflow
87.6/100 · A
github
langgenius/dify
79.1/100 · B
github
open-webui/open-webui
74.8/100 · B
github
google-gemini/gemini-cli
71.8/100 · B
github

What Is Devhelm Demo?

Devhelm Demo is a software tool in the infrastructure category: Demo server with simple tools for testing mcp-recorder.. It has 1 GitHubスター. Nerq Trust Score: 42/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.

How Nerq Assesses Devhelm Demo's Safety

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

The overall Trust Score of 42.5/100 (E) 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 Devhelm Demo?

Devhelm Demo is designed for:

Risk guidance: We recommend caution with Devhelm Demo. The low trust score suggests potential risks in セキュリティ, メンテナンス, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Devhelm Demo'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 Devhelm Demo's dependency tree.
  3. レビュー permissions — Understand what access Devhelm Demo requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Devhelm Demo 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=DevHelm Demo
  6. 確認してください license — Confirm that Devhelm Demo'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 Devhelm Demo

When evaluating whether Devhelm Demo is safe, consider these category-specific risks:

Data handling

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

Dependency セキュリティ

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

Update frequency

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

Third-party integrations

If Devhelm Demo 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 Devhelm Demo's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Devhelm Demo in violation of its license can expose your organization to legal liability.

Best Practices for Using Devhelm Demo Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Devhelm Demo while minimizing risk:

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for セキュリティ advisories

Subscribe to Devhelm Demo'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 Devhelm Demo is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Devhelm Demo?

Even promising tools aren't right for every situation. Consider avoiding Devhelm Demo in these scenarios:

For each scenario, evaluate whether Devhelm Demo's trust score of 42.5/100 meets your organization's risk tolerance. We recommend running a manual セキュリティ assessment alongside the automated Nerq score.

How Devhelm Demo Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score is 62/100. Devhelm Demo's score of 42.5/100 is below the category average of 62/100.

This suggests that Devhelm Demo trails behind many comparable infrastructure tools. Organizations with strict セキュリティ requirements should evaluate whether higher-scoring alternatives better meet their needs.

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 Devhelm Demo 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, Devhelm Demo'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 Devhelm Demo's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=DevHelm Demo&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 Devhelm Demo are strengthening or weakening over time.

Devhelm Demo vs 代替品

In the infrastructure category, Devhelm Demo scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

重要なポイント

よくある質問

Devhelm Demoは安全ですか?
注意が必要です。 DevHelm Demo Nerq信頼スコア42.5/100(E). 最も強いシグナル: メンテナンス (0/100). スコアの基準: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100).
Devhelm Demoの信頼スコアは?
DevHelm Demo: 42.5/100 (E). スコアの基準: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100). 新しいデータが利用可能になるとスコアが更新さ���ます. API: GET nerq.ai/v1/preflight?target=DevHelm Demo
Devhelm Demoのより安全な代替は何ですか?
インフラストラクチャカテゴリでは、 higher-rated alternatives include n8n-io/n8n (78/100), langflow-ai/langflow (88/100), langgenius/dify (79/100). DevHelm Demo scores 42.5/100.
Devhelm Demoの安全性スコアはどのくらいの頻度で更新されますか?
Nerq continuously monitors Devhelm Demo and updates its trust score as new data becomes available. Current: 42.5/100 (E), last 認証済み 2026-04-08. API: GET nerq.ai/v1/preflight?target=DevHelm Demo
規制環境でDevhelm Demoを使用できますか?
Devhelm DemoはNerq認証閾値70に達していません。追加の確認が推奨されます。
API: /v1/preflight Trust Badge API Docs

関連項目

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

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