هل Cli Executor آمن؟

Cli Executor — Nerq درجة الثقة 38.9/100 (الدرجة E). التقييم مبني على 3 independent trust signals.

Cli Executor هو software tool بدرجة ثقة Nerq 38.9/100 (E), بناءً على 3 أبعاد بيانات مستقلة. الصيانة: 0/100. الشعبية: 0/100. البيانات مصدرها قراءة آلية.

هل Cli Executor آمن؟

تفاصيل درجة الثقة — Cli Executor لديه درجة ثقة Nerq تبلغ 38.9/100 (E). Measured across 3 independent trust signals.

تحليل الأمان → تقرير الخصوصية →

ما هي درجة ثقة Cli Executor؟

حصل Cli Executor على درجة ثقة Nerq تبلغ 38.9/100 بدرجة E. يعتمد هذا التقييم على 3 أبعاد مُقاسة بشكل مستقل.

الصيانة
0
التوثيق
0
الشعبية
0

ما هي النتائج الأمنية الرئيسية لـ Cli Executor؟

أقوى إشارة لـ Cli Executor هي الصيانة بدرجة 0/100. لم يتم اكتشاف أي ثغرات أمنية معروفة.

⚠الصيانة: 0/100 — نشاط صيانة منخفض
⚠التوثيق: 0/100 — توثيق محدود
⚠الشعبية: 0/100 — 1 stars on pulsemcp

ما هو Cli Executor ومن يديره؟

المؤلفhttps://github.com/0xbruno/mcpexec
الفئةالبنية التحتية
النجوم1
المصدرhttps://github.com/0xbruno/mcpexec

بدائل شائعة في infrastructure

n8n-io/n8n
69.1/100 · C
github
langflow-ai/langflow
77.0/100 · B
github
langgenius/dify
69.7/100 · C
github
open-webui/open-webui
60.4/100 · C
github
google-gemini/gemini-cli
56.2/100 · D
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 درجة الثقة: 39/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and اعتماد المجتمع.

How Nerq Assesses Cli Executor's Safety

Nerq's درجة الثقة is calculated from 13+ independent signals aggregated into five أبعاد. Here is how Cli Executor performs in each:

The overall درجة الثقة 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:

كيفية read the signals: Cli Executor's measured signals (maintenance 0/100, documentation 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.

كيفية 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 — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for ثغرات أمنية معروفة 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. مراجعة the 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 عملاء 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 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:

Data handling

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.

Dependency security

Check Cli Executor's dependency tree for ثغرات أمنية معروفة. Tools with outdated or unmaintained dependencies pose a higher security 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.

الترخيص and IP compliance

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 compliance with your security policies.

Keep dependencies updated

Ensure Cli Executor and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

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

Monitor for security advisories

Subscribe to Cli Executor's security 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.

Situations That Warrant مستقل 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:

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 درجة الثقة 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 متوسط 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 البدائل

In the infrastructure category, Cli Executor scores 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؟
CLI Executor: 38.9/100 (E). التقييم مبني على الصيانة (0/100), الشعبية (0/100), التوثيق (0/100). يتم تحديث النتائج عند توفر بيانات جديدة. API: GET nerq.ai/v1/preflight?target=CLI Executor
ما هي البدائل الأكثر أمانًا لـ Cli Executor؟
في فئة البنية التحتية، البدائل الأعلى تقييمًا تشمل n8n-io/n8n (69/100), langflow-ai/langflow (77/100), langgenius/dify (70/100). CLI Executor scores 38.9/100.
كم مرة يتم تحديث درجة أمان Cli Executor؟
Nerq recomputes Cli Executor's trust score as new data becomes available. Current: 38.9/100 (E). API: GET nerq.ai/v1/preflight?target=CLI Executor
هل يمكنني استخدام Cli Executor في بيئة منظمة؟
Cli Executor: 38.9/100 (E). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge واجهة برمجة التطبيقات Docs

انظر أيضاً

إخلاء المسؤولية: درجات ثقة Nerq هي تقييمات آلية مبنية على إشارات متاحة للعموم. وهي ليست توصيات أو ضمانات. قم دائمًا بإجراء العناية الواجبة الخاصة بك.

نستخدم ملفات تعريف الارتباط للتحليلات والتخزين المؤقت. الخصوصية