Este Cli Secure sigur?

Cli Secure — Nerq Trust Score 43.5/100 (Nota E). Pe baza analizei a 3 dimensiuni de încredere, este are preocupări de securitate notabile. Ultima actualizare: 2026-04-02.

Fiți precauți cu Cli Secure. Cli Secure is a software tool cu un Scor de Încredere Nerq de 43.5/100 (E), based on 3 dimensiuni independente de date. Este sub pragul recomandat de 70. Mentenanță: 0/100. Popularity: 1/100. Date provenite din multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Ultima actualizare: 2026-04-02. Date citibile de mașină (JSON).

Este Cli Secure sigur?

NU — UTILIZAȚI CU PRECAUȚIE — Cli Secure are un Scor de Încredere Nerq de 43.5/100 (E). Are semnale de încredere sub medie cu lacune semnificative în securitate, mentenanță sau documentație. Nu este recomandat pentru producție fără o revizuire manuală amănunțită și măsuri suplimentare de securitate.

Analiză de Securitate → Raport de confidențialitate {name} →

Care este scorul de încredere al Cli Secure?

Cli Secure are un Scor de Încredere Nerq de 43.5/100, earning a E grade. This score is based on 3 independently measured dimensiuni including securitate, mentenanță, and adoptare comunitară.

Mentenanță
0
Documentație
0
Popularitate
1

Care sunt principalele constatări de securitate pentru Cli Secure?

Cli Secure's strongest signal is popularitate at 1/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Mentenanță: 0/100 — activitate redusă de mentenanță
Documentation: 0/100 — documentație limitată
Popularity: 1/100 — 166 stele pe pulsemcp

Ce este Cli Secure și cine îl întreține?

Autorhttps://github.com/mladensu/cli-mcp-server
Categoriesecuritate
Stele166
Sursăhttps://github.com/mladensu/cli-mcp-server

Alternative populare în securitate

bee-san/Ciphey
73.8/100 · B
github
usestrix/strix
73.8/100 · B
github
SWE-agent/SWE-agent
91.3/100 · A+
github
promptfoo/promptfoo
92.6/100 · A+
github
TecharoHQ/anubis
72.3/100 · B
github

What Is Cli Secure?

Cli Secure is a securitate tool: CLI Secure executes shell commands with strict securitate policies.. It has 166 GitHub stars. Nerq Trust Score: 44/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including securitate vulnerabilities, mentenanță activity, license conformitate, and adoptare comunitară.

How Nerq Assesses Cli Secure's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiuni. Here is how Cli Secure performs in each:

The overall Trust Score of 43.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 Cli Secure?

Cli Secure is designed for:

Risk guidance: We recommend caution with Cli Secure. The low trust score suggests potential risks in securitate, mentenanță, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Cli Secure's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — Verificați repository securitate policy, open issues, and recent commits for signs of active mentenanță.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Cli Secure's dependency tree.
  3. Recenzie permissions — Understand what access Cli Secure requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Cli Secure 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 Secure
  6. Verificați license — Confirm that Cli Secure'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 securitate concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Cli Secure

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

Data handling

Understand how Cli Secure processes, stores, and transmits your data. Verificați tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency securitate

Check Cli Secure's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher securitate risk.

Update frequency

Regularly check for updates to Cli Secure. Securitate patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Cli Secure 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 conformitate

Verify that Cli Secure'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 Secure in violation of its license can expose your organization to legal liability.

Best Practices for Using Cli Secure Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Cli Secure while minimizing risk:

Conduct regular audits

Periodically review how Cli Secure is used in your workflow. Check for unexpected behavior, permissions drift, and conformitate with your securitate policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for securitate advisories

Subscribe to Cli Secure's securitate 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 Secure is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Cli Secure?

Even promising tools aren't right for every situation. Consider avoiding Cli Secure in these scenarios:

scorul de încredere al

For each scenario, evaluate whether Cli Secure de 43.5/100 meets your organization's risk tolerance. We recommend running a manual securitate assessment alongside the automated Nerq score.

How Cli Secure Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among securitate tools, the average Trust Score is 67/100. Cli Secure's score of 43.5/100 is below the category average of 67/100.

This suggests that Cli Secure trails behind many comparable securitate tools. Organizations with strict securitate 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 moderat 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 Secure 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 mentenanță patterns change, Cli Secure'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 securitate and quality. Conversely, a downward trend may signal reduced mentenanță, growing technical debt, or unresolved vulnerabilities. To track Cli Secure's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=CLI Secure&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 — securitate, mentenanță, documentație, conformitate, and community — has evolved independently, providing granular visibility into which aspects of Cli Secure are strengthening or weakening over time.

Cli Secure vs Alternative

În categoria securitate, Cli Secure a obținut scorul 43.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Concluzii principale

Întrebări frecvente

Este Cli Secure sigur de utilizat?
Fiți precauți. CLI Secure are un Scor de Încredere Nerq de 43.5/100 (E). Cel mai puternic semnal: popularitate (1/100). Scor bazat pe mentenanță (0/100), popularitate (1/100), documentație (0/100).
Ce este Cli Secure's trust score?
CLI Secure: 43.5/100 (E). Scor bazat pe: mentenanță (0/100), popularitate (1/100), documentație (0/100). Scorurile se actualizează pe măsură ce devin disponibile date noi. API: GET nerq.ai/v1/preflight?target=CLI Secure
Care sunt alternativele mai sigure la Cli Secure?
În categoria securitate, alternativele cu scor mai mare includ bee-san/Ciphey (74/100), usestrix/strix (74/100), SWE-agent/SWE-agent (91/100). CLI Secure a obținut scorul 43.5/100.
How often is Cli Secure's safety score updated?
Nerq continuously monitors Cli Secure and updates its trust score as new data becomes available. Date provenite din multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 43.5/100 (E), last verificat 2026-04-02. API: GET nerq.ai/v1/preflight?target=CLI Secure
Pot folosi Cli Secure într-un mediu reglementat?
Cli Secure 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: Scorurile de încredere Nerq sunt evaluări automatizate bazate pe semnale disponibile public. Nu sunt recomandări sau garanții. Efectuați întotdeauna propria verificare.

We use cookies for analytics and caching. Confidențialitate Policy