Cli Executor é seguro?
Cli Executor — Nerq Trust Score 38.9/100 (Grau E). Pontuação baseada em 3 independent trust signals.
Cli Executor é um software tool com um Nerq Trust Score de 38.9/100 (E), com base em 3 dimensões de dados independentes. Manutenção: 0/100. Popularidade: 0/100. Dados obtidos de múltiplas fontes públicas incluindo registros de pacotes, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Última atualização: n/a. Dados legíveis por máquina (JSON).
Cli Executor é seguro?
Detalhamento da Pontuação de Confiança — Cli Executor has a Nerq Trust Score of 38.9/100 (E). Measured across 3 independent trust signals.
Qual é a pontuação de confiança de Cli Executor?
Cli Executor tem uma Pontuação de Confiança Nerq de 38.9/100, obtendo grau E. Esta pontuação é baseada em 3 dimensões medidas independentemente.
Quais são as principais descobertas de segurança de Cli Executor?
O sinal mais forte de Cli Executor é manutenção com 0/100. Nenhuma vulnerabilidade conhecida foi detectada.
O que é Cli Executor e quem o mantém?
| Autor | https://github.com/0xbruno/mcpexec |
| Categoria | Infrastructure |
| Stars | 1 |
| Source | https://github.com/0xbruno/mcpexec |
Alternativas Populares em infrastructure
What Is Cli Executor?
Cli Executor is a software tool in the infrastructure category: Provides a tool for executing local CLI commands asynchronously using FastMCP and asyncio, handling command arguments securely and offering error handling for failed commands.. It has 1 GitHub stars. Nerq Trust Score: 39/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including segurança vulnerabilities, manutenção activity, license conformidade, and adoção pela comunidade.
How Nerq Assesses Cli Executor's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensões. Here is how Cli Executor performs in each:
- Manutenção (0/100): Cli Executor 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 documentação, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Baseado em GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 38.9/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 Cli Executor?
Cli Executor is commonly evaluated by:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Cli Executor's measured signals (manutenção 0/100, documentação 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 Cli Executor's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Revise o/a repository segurança policy, open issues, and recent commits for signs of active manutenção.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Cli Executor's dependency tree. - Avaliação permissions — Understand what access Cli Executor requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Cli Executor 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=CLI Executor - Revise o/a license — Confirm that Cli Executor'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 segurança concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Cli Executor
When evaluating whether Cli Executor is safe, consider these category-specific risks:
Understand how Cli Executor processes, stores, and transmits your data. Revise o/a tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Cli Executor's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher segurança risk.
Regularly check for updates to Cli Executor. Segurança patches and bug fixes are only effective if you're running the latest version.
If Cli Executor 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 Cli Executor's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Cli Executor in violation of its license can expose your organization to legal liability.
Best Practices for Using Cli Executor Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Cli Executor while minimizing risk:
Periodically review how Cli Executor is used in your workflow. Check for unexpected behavior, permissions drift, and conformidade with your segurança policies.
Ensure Cli Executor and all its dependencies are running the latest stable versions to benefit from segurança patches.
Grant Cli Executor only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Cli Executor's segurança advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Cli Executor is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Cli Executor
Nerq's signals are one input. In the following situations, evaluate Cli Executor'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 Cli Executor's measured trust score of 38.9/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Cli Executor is suitable for any particular use.
How Cli Executor Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score is 62/100. Cli Executor's score of 38.9/100 is below the category average of 62/100.
This suggests that Cli Executor trails behind many comparable infrastructure tools. Organizations with strict segurança 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 moderado 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 Cli Executor 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 manutenção patterns change, Cli Executor'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 segurança and quality. Conversely, a downward trend may signal reduced manutenção, growing technical debt, or unresolved vulnerabilities. To track Cli Executor's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=CLI Executor&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 — segurança, manutenção, documentação, conformidade, and community — has evolved independently, providing granular visibility into which aspects of Cli Executor are strengthening or weakening over time.
Cli Executor vs Alternativas
In the infrastructure category, Cli Executor scores 38.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Cli Executor vs n8n — Trust Score: 69.1/100
- Cli Executor vs langflow — Trust Score: 77.0/100
- Cli Executor vs dify — Trust Score: 69.7/100
Pontos Principais
- Cli Executor has a measured Nerq Trust Score of 38.9/100 (E) — a composite of independent signals, not a suitability judgment.
- Among infrastructure tools, Cli Executor scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — segurança, manutenção, documentação, conformidade, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Perguntas Frequentes
Cli Executor é seguro?
Qual é a pontuação de confiança de Cli Executor?
Quais são alternativas mais seguras ao Cli Executor?
Com que frequência o score de segurança do Cli Executor é atualizado?
Posso usar Cli Executor em um ambiente regulado?
Veja também
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.