Er Cli Manager Mcp trygt?
Cli Manager Mcp — Nerq Trust Score 62.9/100 (Karakter C). Poeng basert på 5 independent trust signals.
Cli Manager Mcp er en software tool har en Nerq-tillitspoeng på 62.9/100 (C), based on 5 uavhengige datadimensjoner. Sikkerhet: 0/100. Vedlikehold: 1/100. Popularitet: 0/100. Data hentet fra flere offentlige kilder inkludert pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sist oppdatert: n/a. Maskinlesbare data (JSON).
Er Cli Manager Mcp trygt?
Tillitspoeng detaljer — Cli Manager Mcp har en Nerq-tillitspoeng på 62.9/100 (C). Measured across 5 independent trust signals.
Hva er tillitspoengene til Cli Manager Mcp?
Cli Manager Mcp har en Nerq-tillitspoeng på 62.9/100 med karakteren C. Denne poengsummen er basert på 5 uavhengig målte dimensjoner, inkludert sikkerhet, vedlikehold og samfunnsadopsjon.
Hva er de viktigste sikkerhetsfunnene for Cli Manager Mcp?
Cli Manager Mcps sterkeste signal er samsvar på 100/100. Ingen kjente sårbarheter er funnet.
Hva er Cli Manager Mcp og hvem vedlikeholder det?
| Utvikler | yksanjo |
| Kategori | Devops |
| Kilde | https://github.com/yksanjo/cli-manager-mcp |
| Frameworks | anthropic |
| Protocols | mcp · rest |
Regulatorisk samsvar
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Populære alternativer i devops
What Is Cli Manager Mcp?
Cli Manager Mcp is a DevOps tool: AI-Powered Terminal Management for Claude Desktop - MCP server for CLI session and project architecture management.. Nerq Trust Score: 63/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhet vulnerabilities, vedlikehold activity, license samsvar, and fellesskapsadopsjon.
How Nerq Assesses Cli Manager Mcp's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensjoner. Here is how Cli Manager Mcp performs in each:
- Sikkerhet (0/100): Cli Manager Mcp's sikkerhet posture is poor. This score factors in known CVEs, dependency vulnerabilities, sikkerhet policy presence, and code signing practices.
- Vedlikehold (1/100): Cli Manager Mcp is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API dokumentasjon, usage examples, and contribution guidelines.
- Compliance (100/100): Cli Manager Mcp is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Basert på GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 62.9/100 (C) 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 Manager Mcp?
Cli Manager Mcp is commonly evaluated by:
- Developers and teams working with devops tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Cli Manager Mcp's measured signals (sikkerhet 0/100, vedlikehold 1/100, dokumentasjon 1/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.
How to Verify Cli Manager Mcp's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Gjennomgå repository's sikkerhet policy, open issues, and recent commits for signs of active vedlikehold.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for kjente sårbarheter in Cli Manager Mcp's dependency tree. - Anmeldelse permissions — Understand what access Cli Manager Mcp requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Cli Manager Mcp 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-manager-mcp - Gjennomgå license — Confirm that Cli Manager Mcp'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 sikkerhet concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Cli Manager Mcp
When evaluating whether Cli Manager Mcp is safe, consider these category-specific risks:
Understand how Cli Manager Mcp processes, stores, and transmits your data. Gjennomgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Cli Manager Mcp's dependency tree for kjente sårbarheter. Tools with outdated or unmaintained dependencies pose a higher sikkerhet risk.
Regularly check for updates to Cli Manager Mcp. Sikkerhet patches and bug fixes are only effective if you're running the latest version.
If Cli Manager Mcp 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 Manager Mcp'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 Manager Mcp in violation of its license can expose your organization to legal liability.
Cli Manager Mcp and the EU AI Act
Cli Manager Mcp is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.
Nerq's samsvar assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal samsvar.
Best Practices for Using Cli Manager Mcp Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Cli Manager Mcp while minimizing risk:
Periodically review how Cli Manager Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and samsvar with your sikkerhet policies.
Ensure Cli Manager Mcp and all its dependencies are running the latest stable versions to benefit from sikkerhet patches.
Grant Cli Manager Mcp only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Cli Manager Mcp's sikkerhet advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Cli Manager Mcp is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Cli Manager Mcp
Nerq's signals are one input. In the following situations, evaluate Cli Manager Mcp's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Cli Manager Mcp's measured trust score of 62.9/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Cli Manager Mcp is suitable for any particular use.
How Cli Manager Mcp Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Cli Manager Mcp's score of 62.9/100 is near the category average of 63/100.
This places Cli Manager Mcp in line with the typical DevOps tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.
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 Manager Mcp 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 vedlikehold patterns change, Cli Manager Mcp'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 sikkerhet and quality. Conversely, a downward trend may signal reduced vedlikehold, growing technical debt, or unresolved vulnerabilities. To track Cli Manager Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=cli-manager-mcp&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 — sikkerhet, vedlikehold, dokumentasjon, samsvar, and community — has evolved independently, providing granular visibility into which aspects of Cli Manager Mcp are strengthening or weakening over time.
Cli Manager Mcp vs Alternativer
In the devops category, Cli Manager Mcp scores 62.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Cli Manager Mcp vs ansible — Trust Score: 74.9/100
- Cli Manager Mcp vs Flowise — Trust Score: 67.5/100
- Cli Manager Mcp vs learn-claude-code — Trust Score: 76.1/100
Viktigste punkter
- Cli Manager Mcp has a measured Nerq Trust Score of 62.9/100 (C) — a composite of independent signals, not a suitability judgment.
- Among DevOps tools, Cli Manager Mcp scores near the category average of 63/100 (a positional measurement relative to peers).
- The individual signals — sikkerhet, vedlikehold, dokumentasjon, samsvar, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Ofte stilte spørsmål
Er Cli Manager Mcp trygt?
Hva er tillitspoengene til Cli Manager Mcp?
Hva er tryggere alternativer til Cli Manager Mcp?
Hvor ofte oppdateres Cli Manager Mcps sikkerhetspoeng?
Kan jeg bruke Cli Manager Mcp i et regulert miljø?
Se også
Disclaimer: Nerqs tillitspoeng er automatiserte vurderinger basert på offentlig tilgjengelige signaler. De utgjør ikke anbefalinger eller garantier. Utfør alltid din egen verifisering.