Docs Provider è sicuro?
Docs Provider — Nerq Trust Score 42.5/100 (Grado E). Sulla base dell'analisi di 3 dimensioni di fiducia, è ha preoccupazioni di sicurezza notevoli. Ultimo aggiornamento: 2026-04-23.
Fai attenzione con Docs Provider. Docs Provider è un software tool con un Punteggio di fiducia Nerq di 42.5/100 (E), based on 3 dimensioni di dati indipendenti. Sotto la soglia verificata Nerq Manutenzione: 0/100. Popolarità: 0/100. Dati provenienti da molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Ultimo aggiornamento: 2026-04-23. Dati leggibili dalle macchine (JSON).
Docs Provider è sicuro?
NO — USE WITH CAUTION — Docs Provider has a Nerq Trust Score of 42.5/100 (E). Ha segnali di fiducia inferiori alla media con lacune significative in sicurezza, manutenzione, or documentazione. Not recommended for production use without thorough manual review and additional sicurezza measures.
Qual è il punteggio di fiducia di Docs Provider?
Docs Provider ha un Nerq Trust Score di 42.5/100 con voto E. Questo punteggio si basa su 3 dimensioni misurate indipendentemente, tra cui sicurezza, manutenzione e adozione della community.
Quali sono i risultati di sicurezza chiave per Docs Provider?
Il segnale più forte di Docs Provider è manutenzione a 0/100. Non sono state rilevate vulnerabilità note. It has not yet reached the Nerq Verified threshold of 70+.
Cos'è Docs Provider e chi lo mantiene?
| Autore | https://github.com/yassinetk/mcp-docs-provider |
| Categoria | Coding |
| Stelle | 5 |
| Fonte | https://github.com/yassinetk/mcp-docs-provider |
Alternative popolari in coding
What Is Docs Provider?
Docs Provider is a software tool in the coding category: Enables AI models to access and query local technical documentazione.. 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 sicurezza vulnerabilities, manutenzione activity, license conformità, and adozione della comunità.
How Nerq Assesses Docs Provider's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioni. Here is how Docs Provider performs in each:
- Manutenzione (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 documentazione, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Basato su GitHub stars, forks, download counts, and ecosystem integrations.
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 Docs Provider?
Docs Provider is designed for:
- Developers and teams working with coding tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Docs Provider. The low trust score suggests potential risks in sicurezza, manutenzione, or community support. Consider using a more established alternative for any production or sensitive workload.
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 — Controlla repository sicurezza policy, open issues, and recent commits for signs of active manutenzione.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Docs Provider's dependency tree. - Recensione 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 - Controlla 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 sicurezza 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. Controlla 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 sicurezza risk.
Regularly check for updates to Docs Provider. Sicurezza 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 conformità with your sicurezza policies.
Ensure Docs Provider and all its dependencies are running the latest stable versions to benefit from sicurezza patches.
Grant Docs Provider only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Docs Provider's sicurezza 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.
When Should You Avoid Docs Provider?
Even promising tools aren't right for every situation. Consider avoiding Docs Provider in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional conformità review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Docs Provider's trust score of 42.5/100 meets your organization's risk tolerance. We recommend running a manual sicurezza assessment alongside the automated Nerq score.
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 sicurezza 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 moderato 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 manutenzione 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 sicurezza and quality. Conversely, a downward trend may signal reduced manutenzione, 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 — sicurezza, manutenzione, documentazione, conformità, and community — has evolved independently, providing granular visibility into which aspects of Docs Provider are strengthening or weakening over time.
Docs Provider vs Alternative
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: 74.7/100
- Docs Provider vs ollama — Trust Score: 73.8/100
- Docs Provider vs langchain — Trust Score: 71.3/100
Punti chiave
- Docs Provider has a Trust Score of 42.5/100 (E) and is not yet Nerq Verified.
- Docs Provider has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among coding tools, Docs Provider 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.
Analisi dettagliata del punteggio
| Dimension | Score |
|---|---|
| Manutenzione | 0/100 |
| Popolarità | 0/100 |
Basato su 2 dimensioni. Data from molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard.
Quali dati raccoglie Docs Provider?
Privacy assessment for Docs Provider is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.
Docs Provider è sicuro?
Sicurezza score: in fase di valutazione. Review sicurezza practices and consider alternatives with higher sicurezza scores for sensitive use cases.
Nerq monitora questa entità rispetto a NVD, OSV.dev e database di vulnerabilità specifici del registro per la valutazione continua della sicurezza.
Analisi completa: Report di sicurezza di Docs Provider
Come abbiamo calcolato questo punteggio
Docs Provider's trust score of 42.5/100 (E) è calcolato da molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Il punteggio riflette 2 dimensioni indipendenti: manutenzione (0/100), popolarità (0/100). Ogni dimensione ha lo stesso peso per produrre il punteggio di fiducia complessivo.
Nerq analizza oltre 7,5 milioni di entità in 26 registri utilizzando la stessa metodologia, consentendo il confronto diretto tra entità. I punteggi vengono aggiornati continuamente quando sono disponibili nuovi dati.
Questa pagina è stata revisionata l'ultima volta il April 23, 2026. Versione dei dati: 1.0.
Documentazione completa della metodologia · Dati leggibili dalle macchine (JSON API)
Domande frequenti
Docs Provider è sicuro?
Qual è il punteggio di fiducia di Docs Provider?
Quali sono alternative più sicure a Docs Provider?
Con che frequenza viene aggiornato il punteggio di Docs Provider?
Posso usare Docs Provider in un ambiente regolamentato?
Vedi anche
Disclaimer: I punteggi di fiducia Nerq sono valutazioni automatizzate basate su segnali disponibili pubblicamente. Non costituiscono raccomandazioni o garanzie. Effettua sempre la tua verifica personale.