Docs Provider安全吗?
Docs Provider — Nerq Trust Score 42.5/100 (E级). 基于3 independent trust signals的评分。
Docs Provider 是一个software tool Nerq 信任分数 42.5/100(E), 基于3个独立数据维度. 维护: 0/100. 人气度: 0/100. 数据来源于多个公共来源,包括包注册表、GitHub、NVD、OSV.dev和OpenSSF Scorecard。最后更新:n/a。 机器可读数据(JSON).
Docs Provider安全吗?
信任评分详情 — Docs Provider has a Nerq Trust Score of 42.5/100 (E). Measured across 3 independent trust signals.
Docs Provider的信任评分是多少?
Docs Provider 的 Nerq 信任分数为 42.5/100,等级为 E。该分数基于 3 个独立测量的维度,包括安全性、维护和社区采用。
Docs Provider的主要安全发现是什么?
Docs Provider 最强的信号是 维护,为 0/100。 未检测到已知漏洞。
Docs Provider是什么,谁在维护它?
| 开发者 | https://github.com/yassinetk/mcp-docs-provider |
| 类别 | Coding |
| 星标 | 5 |
| 来源 | https://github.com/yassinetk/mcp-docs-provider |
coding中的热门替代品
What Is Docs Provider?
Docs Provider is a software tool in the coding category: Enables AI models to access and query local technical 文档.. It has 5 GitHub stars. 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 Docs Provider's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 维度. Here is how Docs Provider performs in each:
- 维护 (0/100): Docs Provider 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.
- Community (0/100): Community adoption is limited. 基于 GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 42.5/100 (E) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.
Who Typically Evaluates Docs Provider?
Docs Provider is commonly evaluated by:
- Developers and teams working with coding tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Docs Provider's measured signals (维护 0/100, 文档 0/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.
How to Verify Docs Provider'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 Docs Provider's dependency tree. - 评论 permissions — Understand what access Docs Provider requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Docs Provider 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=Docs Provider - 查看 license — Confirm that Docs Provider'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 Docs Provider
When evaluating whether Docs Provider is safe, consider these category-specific risks:
Understand how Docs Provider processes, stores, and transmits your data. 查看 tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Docs Provider's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher 安全性 risk.
Regularly check for updates to Docs Provider. 安全性 patches and bug fixes are only effective if you're running the latest version.
If Docs Provider 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 Docs Provider's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Docs Provider in violation of its license can expose your organization to legal liability.
Best Practices for Using Docs Provider Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Docs Provider while minimizing risk:
Periodically review how Docs Provider is used in your workflow. Check for unexpected behavior, permissions drift, and 合规性 with your 安全性 policies.
Ensure Docs Provider and all its dependencies are running the latest stable versions to benefit from 安全性 patches.
Grant Docs Provider only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Docs Provider's 安全性 advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Docs Provider is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant 独立 Review of Docs Provider
Nerq's signals are one input. In the following situations, evaluate Docs Provider's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Docs Provider's measured trust score of 42.5/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Docs Provider is suitable for any particular use.
How Docs Provider Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Trust Score is 62/100. Docs Provider's score of 42.5/100 is below the category average of 62/100.
This suggests that Docs Provider trails behind many comparable coding 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 Docs Provider 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, Docs Provider'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 Docs Provider's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Docs Provider&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 Docs Provider are strengthening or weakening over time.
Docs Provider vs 替代品
In the coding category, Docs Provider scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Docs Provider vs AutoGPT — Trust Score: 65.3/100
- Docs Provider vs ollama — Trust Score: 64.4/100
- Docs Provider vs langchain — Trust Score: 77.0/100
主要结论
- Docs Provider has a measured Nerq Trust Score of 42.5/100 (E) — a composite of independent signals, not a suitability judgment.
- Among coding tools, Docs Provider scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — 安全性, 维护, 文档, 合规性, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
常见问题
Docs Provider安全吗?
Docs Provider的信任评分是多少?
Docs Provider有哪些更安全的替代品?
Docs Provider的安全评分多久更新一次?
我可以在受监管的环境中使用Docs Provider吗?
另请参阅
Disclaimer: Nerq 信任评分是基于公开信号的自动评估。它们不构成建议或保证。请始终进行自己的验证。