Безопасен ли Cli Executor?

Cli Executor — Nerq Trust Score 38.9/100 (Оценка E). На основе анализа 3 измерений доверия, считается имеющим значительные риски безопасности. Последнее обновление: 2026-04-05.

Будьте осторожны с Cli Executor. Cli Executor — это software tool с рейтингом доверия Nerq 38.9/100 (E), based on 3 независимых показателей данных. Ниже рекомендуемого порога в 70. Обслуживание: 0/100. Популярность: 0/100. Данные из multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Последнее обновление: 2026-04-05. Машинночитаемые данные (JSON).

Безопасен ли Cli Executor?

НЕТ — ИСПОЛЬЗУЙТЕ С ОСТОРОЖНОСТЬЮ — Cli Executor имеет рейтинг доверия Nerq 38.9/100 (E). Сигналы доверия ниже среднего со значительными пробелами в безопасности, обслуживании или документации. Не рекомендуется для продакшена без тщательной ручной проверки и дополнительных мер безопасности.

Анализ безопасности → Отчёт о конфиденциальности {name} →

Каков рейтинг доверия Cli Executor?

Cli Executor имеет Nerq Trust Score 38.9/100 с оценкой E. Этот балл основан на 3 независимо измеренных параметрах, включая безопасность, обслуживание и принятие сообществом.

Обслуживание
0
Документация
0
Популярность
0

Каковы основные выводы по безопасности Cli Executor?

Самый сильный сигнал Cli Executor — обслуживание на уровне 0/100. Известных уязвимостей не обнаружено. It has not yet reached the Nerq Verified threshold of 70+.

Обслуживание: 0/100 — низкая активность поддержки
Documentation: 0/100 — ограниченная документация
Популярность: 0/100 — 1 звёзд на pulsemcp

Что такое Cli Executor и кто его поддерживает?

Разработчикhttps://github.com/0xbruno/mcpexec
Категорияinfrastructure
Звёзды1
Источникhttps://github.com/0xbruno/mcpexec

Популярные альтернативы в infrastructure

n8n-io/n8n
78.5/100 · B
github
langflow-ai/langflow
87.6/100 · A
github
langgenius/dify
79.1/100 · B
github
open-webui/open-webui
74.8/100 · B
github
google-gemini/gemini-cli
71.8/100 · B
github

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 безопасность vulnerabilities, обслуживание activity, license соответствие, and принятие сообществом.

How Nerq Assesses Cli Executor's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five показателей. Here is how Cli Executor performs in each:

The overall Trust Score 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:

Risk guidance: We recommend caution with Cli Executor. The low trust score suggests potential risks in безопасность, обслуживание, 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:

  1. Check the source code — Проверьте repository безопасность policy, open issues, and recent commits for signs of active обслуживание.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Cli Executor's dependency tree.
  3. Отзыв permissions — Understand what access Cli Executor requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Cli Executor in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=CLI Executor
  6. Проверьте 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.
  7. 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 Cli Executor

When evaluating whether Cli Executor is safe, consider these category-specific risks:

Data handling

Understand how Cli Executor processes, stores, and transmits your data. Проверьте tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency безопасность

Check Cli Executor's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher безопасность risk.

Update frequency

Regularly check for updates to Cli Executor. Безопасность patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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.

License and IP соответствие

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:

Conduct regular audits

Periodically review how Cli Executor is used in your workflow. Check for unexpected behavior, permissions drift, and соответствие with your безопасность policies.

Keep dependencies updated

Ensure Cli Executor and all its dependencies are running the latest stable versions to benefit from безопасность patches.

Follow least privilege

Grant Cli Executor only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for безопасность advisories

Subscribe to Cli Executor's безопасность advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

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:

рейтинг доверия

For each scenario, evaluate whether Cli Executor 38.9/100 meets your organization's risk tolerance. We recommend running a manual безопасность 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 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 безопасность 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 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 обслуживание 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 безопасность and quality. Conversely, a downward trend may signal reduced обслуживание, 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 — безопасность, обслуживание, документация, соответствие, and community — has evolved independently, providing granular visibility into which aspects of Cli Executor are strengthening or weakening over time.

Cli Executor vs Альтернативы

В категории infrastructure, Cli Executor получает 38.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Основные выводы

Часто задаваемые вопросы

Безопасен ли Cli Executor для использования?
Будьте осторожны. CLI Executor имеет рейтинг доверия Nerq 38.9/100 (E). Самый сильный сигнал: обслуживание (0/100). Рейтинг основан на обслуживание (0/100), популярность (0/100), документация (0/100).
Что такое Cli Executor's trust score?
CLI Executor: 38.9/100 (E). Рейтинг основан на: обслуживание (0/100), популярность (0/100), документация (0/100). Рейтинги обновляются по мере поступления новых данных. API: GET nerq.ai/v1/preflight?target=CLI Executor
Какие более безопасные альтернативы Cli Executor?
В категории infrastructure, альтернативы с более высоким рейтингом: n8n-io/n8n (78/100), langflow-ai/langflow (88/100), langgenius/dify (79/100). CLI Executor получает 38.9/100.
How often is Cli Executor's safety score updated?
Nerq continuously monitors Cli Executor and updates its trust score as new data becomes available. Данные из multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 38.9/100 (E), last верифицировано 2026-04-05. API: GET nerq.ai/v1/preflight?target=CLI Executor
Можно ли использовать Cli Executor в регулируемой среде?
Cli Executor has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Рейтинги доверия Nerq — это автоматические оценки, основанные на публично доступных сигналах. Они не являются рекомендацией или гарантией. Всегда проводите собственную проверку.

We use cookies for analytics and caching. Конфиденциальность Policy