Ist Command Proxy sicher?

Ist Command Proxy sicher?

Vertrauensbewertung im Detail — Command Proxy has a Nerq Trust Score of 40.2/100 (E). Measured across 3 independent trust signals.

What Is Command Proxy?

Command Proxy is a DevOps tool: Proxy server for CLI commands managing Expo development tools.. It has 12 GitHub-Sternen. Nerq Trust Score: 40/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.

How Nerq Assesses Command Proxy's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five Dimensionen. Here is how Command Proxy performs in each:

• Wartung (0/100): Command Proxy is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
• Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API Dokumentation, usage examples, and contribution guidelines.
• Community (0/100): Community adoption is limited. Basierend auf GitHub-Sternen, forks, download counts, and ecosystem integrations.

The overall Trust Score of 40.2/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 Command Proxy?

Command Proxy 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: Command Proxy's measured signals (Wartung 0/100, Dokumentation 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.

How to Verify Command Proxy's Safety Yourself

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

1. Check the source code — Überprüfen Sie das/die repository Sicherheit policy, open issues, and recent commits for signs of active Wartung.
2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Command Proxy's dependency tree.
3. Bewertung permissions — Understand what access Command Proxy requires. Software tools should follow the principle of least privilege.
4. Test in isolation — Run Command Proxy 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=Command Proxy
6. Überprüfen Sie das/die license — Confirm that Command Proxy'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 Sicherheit concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Command Proxy

When evaluating whether Command Proxy is safe, consider these category-specific risks:

Best Practices for Using Command Proxy Safely

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

Situations That Warrant Independent Review of Command Proxy

Nerq's signals are one input. In the following situations, evaluate Command Proxy'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 Command Proxy's measured trust score of 40.2/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Command Proxy is suitable for any particular use.

How Command Proxy 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. Command Proxy's score of 40.2/100 is below the category average of 63/100.

This suggests that Command Proxy trails behind many comparable DevOps tools. Organizations with strict Sicherheit 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 Command Proxy 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 Wartung patterns change, Command Proxy'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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, growing technical debt, or unresolved vulnerabilities. To track Command Proxy's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Command Proxy&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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Command Proxy are strengthening or weakening over time.

Command Proxy vs Alternativen

In the devops category, Command Proxy scores 40.2/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Command Proxy vs ansible — Trust Score: 74.9/100
• Command Proxy vs Flowise — Trust Score: 67.5/100
• Command Proxy vs learn-claude-code — Trust Score: 72.1/100

Wichtigste Punkte

• Command Proxy has a measured Nerq Trust Score of 40.2/100 (E) — a composite of independent signals, not a suitability judgment.
• Among DevOps tools, Command Proxy scores below the category average of 63/100 (a positional measurement relative to peers).
• The individual signals — Sicherheit, Wartung, Dokumentation, Konformität, community — are shown above. Weigh them against your own requirements.
• Query the current measured values via Nerq's Preflight API.