Droid Cli é seguro?
Droid Cli — Nerq Trust Score 42.5/100 (Grau E). Com base na análise de 3 dimensões de confiança, é tem preocupações de segurança notáveis. Última atualização: 2026-04-01.
Tenha cautela com Droid Cli. Droid Cli is a software tool com uma Pontuação de Confiança Nerq de 42.5/100 (E), based on 3 independent data dimensions. It is below the recommended threshold of 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Dados legíveis por máquina (JSON).
Droid Cli é seguro?
NO — USE WITH CAUTION — Droid Cli tem uma Pontuação de Confiança Nerq de 42.5/100 (E). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.
Qual é a pontuação de confiança de Droid Cli?
Droid Cli tem uma Pontuação de Confiança Nerq de 42.5/100, obtendo grau E. Esta pontuação é baseada em 3 dimensões medidas independentemente.
Quais são as principais descobertas de segurança de Droid Cli?
O sinal mais forte de Droid Cli é manutenção com 0/100. Nenhuma vulnerabilidade conhecida foi detectada. Ainda não atingiu o limiar verificado Nerq de 70+.
O que é Droid Cli e quem o mantém?
| Autor | https://github.com/zcg/droid-mcp-rs |
| Categoria | coding |
| Stars | 2 |
| Source | https://github.com/zcg/droid-mcp-rs |
Alternativas Populares em coding
What Is Droid Cli?
Droid Cli is a software tool in the coding category: Droid CLI is an AI agent for AI-assisted coding tasks with configurable autonomy levels and safety controls.. It has 2 GitHub stars. Nerq Trust Score: 42/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Droid Cli's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Droid Cli performs in each:
- Manutenção (0/100): Droid Cli 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 documentation, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Based on 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 Droid Cli?
Droid Cli 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 Droid Cli. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Droid Cli's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Droid Cli's dependency tree. - Avaliação permissions — Understand what access Droid Cli requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Droid Cli 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=Droid CLI - Revise o/a license — Confirm that Droid Cli'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Droid Cli
When evaluating whether Droid Cli is safe, consider these category-specific risks:
Understand how Droid Cli processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Droid Cli's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Droid Cli. Security patches and bug fixes are only effective if you're running the latest version.
If Droid Cli 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 Droid Cli's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Droid Cli in violation of its license can expose your organization to legal liability.
Best Practices for Using Droid Cli Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Droid Cli while minimizing risk:
Periodically review how Droid Cli is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Droid Cli and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Droid Cli only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Droid Cli's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Droid Cli is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Droid Cli?
Even promising tools aren't right for every situation. Consider avoiding Droid Cli in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional compliance review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Droid Cli de 42.5/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.
How Droid Cli 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. Droid Cli's score of 42.5/100 is below the category average of 62/100.
This suggests that Droid Cli trails behind many comparable coding tools. Organizations with strict security 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 moderate 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 Droid Cli 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 maintenance patterns change, Droid Cli'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 security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Droid Cli's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Droid CLI&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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Droid Cli are strengthening or weakening over time.
Droid Cli vs Alternatives
In the coding category, Droid Cli scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Droid Cli vs AutoGPT — Trust Score: 74.7/100
- Droid Cli vs ollama — Trust Score: 73.8/100
- Droid Cli vs langchain — Trust Score: 86.4/100
Pontos Principais
- Droid Cli tem uma Pontuação de Confiança de 42.5/100 (E) and is not yet Nerq Verified.
- Droid Cli has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among coding tools, Droid Cli 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.
Perguntas Frequentes
É Droid Cli seguro para usar?
O que é Droid Cli's trust score?
Quais são alternativas mais seguras a Droid Cli?
How often is Droid Cli's safety score updated?
Can I use Droid Cli in a regulated environment?
Disclaimer: As pontuações de confiança da Nerq são avaliações automatizadas baseadas em sinais publicamente disponíveis. Não são endossos ou garantias. Sempre realize sua própria verificação.