Dingding Botは安全ですか?

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

Dingding Botには注意が必要です。 Dingding Bot はsoftware toolです Nerq信頼スコア44.7/100(E), 3つの独立したデータ次元に基づく. It is below the recommended threshold of 70. メンテナンス: 0/100. 人気度: 0/100. データソース: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. 最終更新: 2026-04-04. 機械可読データ(JSON).

Dingding Botは安全ですか?

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

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

Dingding Botの信頼スコアは?

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

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

Dingding Botの主なセキュリティ調査結果は?

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

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

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

作者https://github.com/shawyeok/mcp-dingding-bot
カテゴリcommunication
Stars12
Sourcehttps://github.com/shawyeok/mcp-dingding-bot

communicationの人気の代替品

CorentinJ/Real-Time-Voice-Cloning
71.3/100 · B
github
lencx/ChatGPT
73.8/100 · B
github
janhq/jan
73.8/100 · B
github
2noise/ChatTTS
73.8/100 · B
github
chatboxai/chatbox
73.8/100 · B
github

What Is Dingding Bot?

Dingding Bot is a software tool in the communication category: DingDing Bot integrates with DingDing to send automated notifications.. It has 12 GitHub stars. Nerq Trust Score: 45/100 (E).

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

How Nerq Assesses Dingding Bot's Safety

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

The overall Trust Score of 44.7/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 Dingding Bot?

Dingding Bot is designed for:

Risk guidance: We recommend caution with Dingding Bot. 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 Dingding Bot'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 Dingding Bot's dependency tree.
  3. レビュー permissions — Understand what access Dingding Bot requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Dingding Bot 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=DingDing Bot
  6. 確認してください license — Confirm that Dingding Bot'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 Dingding Bot

When evaluating whether Dingding Bot is safe, consider these category-specific risks:

Data handling

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

Dependency セキュリティ

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

Update frequency

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

Third-party integrations

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

Best Practices for Using Dingding Bot Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for セキュリティ advisories

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

When Should You Avoid Dingding Bot?

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

For each scenario, evaluate whether Dingding Botの信頼スコア 44.7/100 meets your organization's risk tolerance. We recommend running a manual セキュリティ assessment alongside the automated Nerq score.

How Dingding Bot 比較s to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among communication tools, the average Trust Score is 62/100. Dingding Bot's score of 44.7/100 is below the category average of 62/100.

This suggests that Dingding Bot trails behind many comparable communication 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 Dingding Bot 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, Dingding Bot'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 Dingding Bot's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=DingDing Bot&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 Dingding Bot are strengthening or weakening over time.

Dingding Bot vs 代替品

In the communication category, Dingding Bot scores 44.7/100. There are higher-scoring alternatives available. For a detailed comparison, see:

重要なポイント

よくある質問

Is Dingding Bot 安全に使用できます?
注意が必要です。 DingDing Bot のNerq信頼スコアは 44.7/100 (E). 最も強いシグナル: メンテナンス (0/100). スコアの基準: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100).
Dingding Bot's trust scoreとは?
DingDing Bot: 44.7/100 (E). スコアの基準:: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=DingDing Bot
Dingding Botのより安全な代替品は?
In the communication category, higher-rated alternatives include CorentinJ/Real-Time-Voice-Cloning (71/100), lencx/ChatGPT (74/100), janhq/jan (74/100). DingDing Bot scores 44.7/100.
How often is Dingding Bot's safety score updated?
Nerq continuously monitors Dingding Bot and updates its trust score as new data becomes available. データソース: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 44.7/100 (E), last 認証済み 2026-04-04. API: GET nerq.ai/v1/preflight?target=DingDing Bot
Can I use Dingding Bot in a regulated environment?
Dingding Bot 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の信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。

We use cookies for analytics and caching. プライバシー Policy