Er Run Shell Command sikker?

Run Shell Command — Nerq Trust Score 34.4/100 (Karakter E). Baseret på analyse af 5 tillidsdimensioner vurderes det som har betydelige sikkerhedsrisici. Sidst opdateret: 2026-04-05.

Vær forsigtig med Run Shell Command. Run Shell Command er en software tool med en Nerq Tillidsscore på 34.4/100 (E). Under Nerqs verificerede tærskel Data hentet fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sidst opdateret: 2026-04-05. Maskinlæsbare data (JSON).

Er Run Shell Command sikker?

NO — USE WITH CAUTION — Run Shell Command has a Nerq Trust Score of 34.4/100 (E). Har under gennemsnitlige tillidssignaler med betydelige huller in sikkerhed, vedligeholdelse, or dokumentation. Not recommended for production use without thorough manual review and additional sikkerhed measures.

Sikkerhedsanalyse → Run Shell Command privatlivsrapport →

Hvad er Run Shell Commands tillidsscore?

Run Shell Command har en Nerq Trust Score på 34.4/100 med karakteren E. Denne score er baseret på 5 uafhængigt målte dimensioner, herunder sikkerhed, vedligeholdelse og community-adoption.

Samlet tillid
34.4

Hvad er de vigtigste sikkerhedsresultater for Run Shell Command?

Run Shell Commands stærkeste signal er samlet tillid på 34.4/100. Ingen kendte sårbarheder er fundet. It has not yet reached the Nerq Verified threshold of 70+.

Samlet tillidsscore: 34.4/100 på tværs af alle tilgængelige signaler

Hvad er Run Shell Command og hvem vedligeholder det?

Udviklerhttps://github.com/benyue1978/run-command-mcp
KategoriUncategorized
Kildehttps://github.com/benyue1978/run-command-mcp

What Is Run Shell Command?

Run Shell Command is a software tool in the uncategorized category: Enables direct execution of shell commands from chat interfaces, creating a bridge between natural language prompts and local system operations for quick developer workflows.. Nerq Trust Score: 34/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhed vulnerabilities, vedligeholdelse activity, license overholdelse, and fællesskabsadoption.

How Nerq Assesses Run Shell Command's Safety

Nerq evaluates every software tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core dimensioner: Sikkerhed (known CVEs, dependency vulnerabilities, sikkerhed policies), Vedligeholdelse (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).

Run Shell Command receives an overall Trust Score of 34.4/100 (E), which Nerq considers low. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=Run Shell Command

Each dimension is weighted according to its importance for the tool's category. For example, Sikkerhed and Vedligeholdelse carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Run Shell Command's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimensioner, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).

Who Should Use Run Shell Command?

Run Shell Command is designed for:

Risk guidance: We recommend caution with Run Shell Command. The low trust score suggests potential risks in sikkerhed, vedligeholdelse, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Run Shell Command's Safety Yourself

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

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

Common Safety Concerns with Run Shell Command

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

Data handling

Understand how Run Shell Command processes, stores, and transmits your data. Gennemgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sikkerhed

Check Run Shell Command's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sikkerhed risk.

Update frequency

Regularly check for updates to Run Shell Command. Sikkerhed patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Run Shell Command 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 overholdelse

Verify that Run Shell Command's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Run Shell Command in violation of its license can expose your organization to legal liability.

Best Practices for Using Run Shell Command Safely

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

Conduct regular audits

Periodically review how Run Shell Command is used in your workflow. Check for unexpected behavior, permissions drift, and overholdelse with your sikkerhed policies.

Keep dependencies updated

Ensure Run Shell Command and all its dependencies are running the latest stable versions to benefit from sikkerhed patches.

Follow least privilege

Grant Run Shell Command only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for sikkerhed advisories

Subscribe to Run Shell Command's sikkerhed 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 Run Shell Command is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Run Shell Command?

Even promising tools aren't right for every situation. Consider avoiding Run Shell Command in these scenarios:

For each scenario, evaluate whether Run Shell Command's trust score of 34.4/100 meets your organization's risk tolerance. We recommend running a manual sikkerhed assessment alongside the automated Nerq score.

How Run Shell Command Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Run Shell Command's score of 34.4/100 is below the category average of 62/100.

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

Vigtigste pointer

Ofte stillede spørgsmål

Er Run Shell Command sikker?
Vær forsigtig. Run Shell Command med en Nerq Tillidsscore på 34.4/100 (E). Stærkeste signal: samlet tillid (34.4/100). Score baseret på multiple trust dimensioner.
Hvad er Run Shell Commands tillidsscore?
Run Shell Command: 34.4/100 (E). Score baseret på multiple trust dimensioner. Scorer opdateres når nye data bliver tilgængelige. API: GET nerq.ai/v1/preflight?target=Run Shell Command
What are safer alternatives to Run Shell Command?
I kategorien Uncategorized, more software tools are being analyzed — check back soon. Run Shell Command scores 34.4/100.
How often is Run Shell Command's safety score updated?
Nerq continuously monitors Run Shell Command and updates its trust score as new data becomes available. Data hentet fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Current: 34.4/100 (E), last verificeret 2026-04-05. API: GET nerq.ai/v1/preflight?target=Run Shell Command
Can I use Run Shell Command in a regulated environment?
Run Shell Command has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Se også

Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.

Vi bruger cookies til analyse og caching. Privatliv