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-23.

Fiți precauți cu Cli Secure. Cli Secure este un software tool cu un Scor de Încredere Nerq de 43.5/100 (E), based on 3 dimensiuni independente de date. Sub pragul verificat Nerq Mentenanță: 0/100. Popularitate: 1/100. Date provenite din multiple surse publice inclusiv registre de pachete, GitHub, NVD, OSV.dev și OpenSSF Scorecard. Ultima actualizare: 2026-04-23. Date citibile de mașină (JSON).

Este Cli Secure sigur?

NO — USE WITH CAUTION — Cli Secure has a Nerq Trust Score of 43.5/100 (E). Are semnale de încredere sub medie cu lacune semnificative in securitate, mentenanță, or documentație. Not recommended for production use without thorough manual review and additional securitate measures.

Analiză de Securitate → Raport de confidențialitate Cli Secure →

Care este scorul de încredere al Cli Secure?

Cli Secure are un Nerq Trust Score de 43.5/100 cu nota E. Acest scor se bazează pe 3 dimensiuni măsurate independent, inclusiv securitate, întreținere și adopție comunitară.

Mentenanță
0
Documentație
0
Popularitate
1

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

Cel mai puternic semnal al Cli Secure este popularitate la 1/100. Nu au fost detectate vulnerabilități cunoscute. It has not yet reached the Nerq Verified threshold of 70+.

Mentenanță: 0/100 — activitate redusă de întreținere
Documentație: 0/100 — documentare limitată
Popularitate: 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
69.9/100 · B-
github
usestrix/strix
69.6/100 · B-
github
SWE-agent/SWE-agent
68.8/100 · B-
github
promptfoo/promptfoo
66.2/100 · B-
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:

For each scenario, evaluate whether Cli Secure's trust score of 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

In the securitate category, Cli Secure scores 43.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Concluzii principale

Analiză detaliată a scorului

DimensionScore
Mentenanță0/100
Popularitate1/100

Bazat pe 2 dimensiuni. Data from multiple surse publice inclusiv registre de pachete, GitHub, NVD, OSV.dev și OpenSSF Scorecard.

Ce date colectează Cli Secure?

Confidențialitate assessment for Cli Secure is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Este Cli Secure sigur?

Securitate score: în evaluare. Review securitate practices and consider alternatives with higher securitate scores for sensitive use cases.

Nerq monitorizează această entitate față de NVD, OSV.dev și bazele de date de vulnerabilități specifice registrului pentru evaluarea continuă a securității.

Analiză completă: Raport de securitate Cli Secure

Cum am calculat acest scor

Cli Secure's trust score of 43.5/100 (E) este calculat din multiple surse publice inclusiv registre de pachete, GitHub, NVD, OSV.dev și OpenSSF Scorecard. Scorul reflectă 2 dimensiuni independente: mentenanță (0/100), popularitate (1/100). Fiecare dimensiune are pondere egală pentru a produce scorul de încredere compus.

Nerq analizează peste 7,5 milioane de entități din 26 de registre folosind aceeași metodologie, permițând compararea directă între entități. Scorurile sunt actualizate continuu pe măsură ce devin disponibile date noi.

Această pagină a fost revizuită ultima dată pe April 23, 2026. Versiunea datelor: 1.0.

Documentație completă a metodologiei · Date citibile de mașină (JSON API)

Întrebări frecvente

Este Cli Secure sigur?
Fiți precauți. CLI Secure cu 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).
Care este scorul de încredere al Cli Secure?
CLI Secure: 43.5/100 (E). Scor bazat pe Mentenanță (0/100), Popularitate (1/100), Documentație (0/100). Scorurile se actualizează când devin disponibile date noi. API: GET nerq.ai/v1/preflight?target=CLI Secure
Care sunt alternative mai sigure la Cli Secure?
În categoria Securitate, higher-rated alternatives include bee-san/Ciphey (70/100), usestrix/strix (70/100), SWE-agent/SWE-agent (69/100). CLI Secure scores 43.5/100.
Cât de des este actualizat scorul de securitate al Cli Secure?
Nerq continuously monitors Cli Secure and updates its trust score as new data becomes available. Current: 43.5/100 (E), last verificat 2026-04-23. API: GET nerq.ai/v1/preflight?target=CLI Secure
Pot folosi Cli Secure într-un mediu reglementat?
Cli Secure nu a atins pragul de verificare Nerq de 70. Se recomandă verificare suplimentară.
API: /v1/preflight Trust Badge API Docs

Vezi și

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.

Folosim cookie-uri pentru analiză și cache. Confidențialitate