Botpress Twoは安全ですか?
Botpress Two — Nerq Trust Score 50.8/100 (Dグレード). 5つの信頼次元の分析に基づき、顕著なセキュリティ上の懸念があると評価されています。 最終更新:2026-04-10。
Botpress Twoは注意して使用してください。 Botpress Two はsoftware toolです (chatbot - botpress intent2) Nerq信頼スコア50.8/100(D), 5つの独立したデータ次元に基づく. Nerq認証閾値未満 セキュリティ: 0/100. メンテナンス: 0/100. 人気度: 0/100. データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. 最終更新: 2026-04-10. 機械可読データ(JSON).
Botpress Twoは安全ですか?
CAUTION — Botpress Two has a Nerq Trust Score of 50.8/100 (D). 中程度の信頼シグナルがありますが、一部懸念される領域があります that warrant attention. Suitable for development use — review セキュリティ and メンテナンス signals before production deployment.
Botpress Twoの信頼スコアは?
Botpress TwoのNerq信頼スコアは50.8/100で、Dグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む5の独立した次元に基づいています。
Botpress Twoの主なセキュリティ調査結果は?
Botpress Twoの最も強いシグナルはコンプライアンスで81/100です。 既知の脆弱性は検出されていません。 Nerq認証閾値70+にまだ達していません。
Botpress Twoとは何で、誰が管理していますか?
| 作者 | joseelias1997 |
| カテゴリ | Uncategorized |
| Source | https://hub.docker.com/r/joseelias1997/botpress-two |
| Protocols | docker |
規制コンプライアンス
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 81/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
What Is Botpress Two?
Botpress Two is a software tool in the uncategorized category: chatbot - botpress intent2. Nerq Trust Score: 51/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.
How Nerq Assesses Botpress Two's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 次元. Here is how Botpress Two performs in each:
- セキュリティ (0/100): Botpress Two's セキュリティ posture is poor. This score factors in known CVEs, dependency vulnerabilities, セキュリティ policy presence, and code signing practices.
- メンテナンス (0/100): Botpress Two is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API ドキュメント, usage examples, and contribution guidelines.
- Compliance (81/100): Botpress Two is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. に基づく GitHubスター, forks, download counts, and ecosystem integrations.
The overall Trust Score of 50.8/100 (D) 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 Botpress Two?
Botpress Two 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: Botpress Two 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 Botpress Two's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — 確認してください repository セキュリティ policy, open issues, and recent commits for signs of active メンテナンス.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Botpress Two's dependency tree. - レビュー permissions — Understand what access Botpress Two requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Botpress Two 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=botpress-two - 確認してください license — Confirm that Botpress Two'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 セキュリティ concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Botpress Two
When evaluating whether Botpress Two is safe, consider these category-specific risks:
Understand how Botpress Two processes, stores, and transmits your data. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Botpress Two's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.
Regularly check for updates to Botpress Two. セキュリティ patches and bug fixes are only effective if you're running the latest version.
If Botpress Two 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 Botpress Two's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Botpress Two in violation of its license can expose your organization to legal liability.
Best Practices for Using Botpress Two Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Botpress Two while minimizing risk:
Periodically review how Botpress Two is used in your workflow. Check for unexpected behavior, permissions drift, and コンプライアンス with your セキュリティ policies.
Ensure Botpress Two and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.
Grant Botpress Two only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Botpress Two's セキュリティ advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Botpress Two is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Botpress Two?
Even promising tools aren't right for every situation. Consider avoiding Botpress Two in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional コンプライアンス review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Botpress Two's trust score of 50.8/100 meets your organization's risk tolerance. We recommend running a manual セキュリティ assessment alongside the automated Nerq score.
How Botpress Two 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. Botpress Two's score of 50.8/100 is below the category average of 62/100.
This suggests that Botpress Two trails behind many comparable uncategorized 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 Botpress Two 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, Botpress Two'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 Botpress Two's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=botpress-two&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 Botpress Two are strengthening or weakening over time.
重要なポイント
- Botpress Two has a Trust Score of 50.8/100 (D) and is not yet Nerq Verified.
- Botpress Two shows 中程度 trust signals. Conduct thorough due diligence before deploying to production environments.
- Among uncategorized tools, Botpress Two scores below the category average of 62/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
よくある質問
Botpress Twoは安全ですか?
Botpress Twoの信頼スコアは?
Botpress Twoのより安全な代替は何ですか?
Botpress Twoの安全性スコアはどのくらいの頻度で更新されますか?
規制環境でBotpress Twoを使用できますか?
関連項目
Disclaimer: Nerqの信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。