Cli Executor安全吗?
Cli Executor — Nerq 信任评分 38.9/100 (E级). 基于3个信任维度的分析,被评估为存在重大安全风险。 最后更新:2026-03-30。
请对Cli Executor保持警惕。 Cli Executor is a software tool Nerq 信任评分为 38.9/100 (E), based on 3 independent data dimensions. 低于推荐阈值 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-03-30. 机器可读数据(JSON).
Cli Executor安全吗?
否——请谨慎使用 — Cli Executor Nerq 信任评分为 38.9/100 (E). 信任信号低于平均水平,在安全性、维护或文档方面存在重大缺口. 未经彻底手动审查和额外安全措施,不建议用于生产环境.
Cli Executor的信任评分是多少?
Cli Executor Nerq 信任评分为 38.9/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.
Cli Executor的主要安全发现是什么?
Cli Executor's strongest signal is 维护 at 0/100. No 已知漏洞 have been detected. It has not yet reached the Nerq Verified threshold of 70+.
Cli Executor是什么,谁在维护它?
| 开发者 | https://github.com/0xbruno/mcpexec |
| 类别 | infrastructure |
| 星标 | 1 |
| 来源 | https://github.com/0xbruno/mcpexec |
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 信任评分: 39/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 Cli Executor's Safety
Nerq's 信任评分 is calculated from 13+ independent signals aggregated into five dimensions. Here is how Cli Executor performs in each:
- 维护 (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 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 信任评分 of 38.9/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 Cli Executor?
Cli Executor is designed for:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Cli Executor. 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 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 — 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 已知漏洞 in Cli Executor's dependency tree. - 评论 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 - 查看 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 security 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. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Cli Executor's dependency tree for 已知漏洞. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Cli Executor. Security 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 compliance with your security policies.
Ensure Cli Executor and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Cli Executor only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Cli Executor's security 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.
When Should You Avoid Cli Executor?
Even promising tools aren't right for every situation. Consider avoiding Cli Executor 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 Cli Executor的信任评分为 38.9/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.
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 信任评分 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 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.
信任评分 History
Nerq continuously monitors Cli Executor and recalculates its 信任评分 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, 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 security and quality. Conversely, a downward trend may signal reduced maintenance, 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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Cli Executor are strengthening or weakening over time.
Cli Executor vs Alternatives
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 — 信任评分: 78.5/100
- Cli Executor vs langflow — 信任评分: 87.6/100
- Cli Executor vs dify — 信任评分: 79.1/100
主要结论
- Cli Executor has a 信任评分 of 38.9/100 (E) and is not yet Nerq Verified.
- Cli Executor has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among infrastructure tools, Cli Executor 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.
常见问题
Cli Executor可以安全使用吗?
Cli Executor's trust score是什么?
Cli Executor有哪些更安全的替代品?
How often is Cli Executor's safety score updated?
我可以在受监管环境中使用Cli Executor吗?
Disclaimer: Nerq 信任评分是基于公开信号的自动评估。它们不构成建议或保证。请始终进行自己的验证。