Er Code Executor Mcp sikker?

Er Code Executor Mcp sikker?

FORSIGTIGHED — Code Executor Mcp has a Nerq Tillidsscore of 60.2/100 (C). Har moderate tillidssignaler, men viser nogle bekymrende områder, der kræver opmærksomhed. Egnet til udviklingsformål — gennemgå sikkerheds- og vedligeholdelsessignaler før produktionsimplementering.

What Is Code Executor Mcp?

Code Executor Mcp is a software tool in the coding category: Code Executor MCP efficiently manages and executes code, reducing token usage.. Nerq Tillidsscore: 60/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Code Executor Mcp's Safety

Nerq's Tillidsscore is calculated from 13+ independent signals aggregated into five dimensions. Here is how Code Executor Mcp performs in each:

• Sikkerhed (0/100): Code Executor Mcp's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
• Vedligeholdelse (1/100): Code Executor 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 documentation, usage examples, and contribution guidelines.
• Compliance (100/100): Code Executor 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. Based on GitHub stars, forks, download counts, and ecosystem integrations.

The overall Tillidsscore of 60.2/100 (C) 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 Code Executor Mcp?

Code Executor Mcp is designed for:

• Developers and teams working with coding tools
• Organizations evaluating AI tools for their stack
• Researchers exploring AI capabilities in this domain

Risk guidance: Code Executor Mcp is suitable for development and testing environments. Before production deployment, conduct a thorough review of its security posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Code Executor Mcp's Safety Yourself

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

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

Common Safety Concerns with Code Executor Mcp

When evaluating whether Code Executor Mcp is safe, consider these category-specific risks:

Code Executor Mcp and the EU AI Act

Code Executor 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 compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.

Best Practices for Using Code Executor Mcp Safely

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

When Should You Avoid Code Executor Mcp?

Even promising tools aren't right for every situation. Consider avoiding Code Executor Mcp in these scenarios:

• Production environments handling sensitive customer data
• Regulated industries (healthcare, finance, government) without additional compliance review
• Mission-critical systems where downtime has significant business impact

For each scenario, evaluate whether Code Executor Mcp 60.2/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Code Executor Mcp Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Tillidsscore is 62/100. Code Executor Mcp's score of 60.2/100 is near the category average of 62/100.

This places Code Executor Mcp in line with the typical coding 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 moderate 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.

Tillidsscore History

Nerq continuously monitors Code Executor Mcp and recalculates its Tillidsscore 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 maintenance patterns change, Code Executor 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 security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Code Executor Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=code-executor-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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Code Executor Mcp are strengthening or weakening over time.

Code Executor Mcp vs Alternatives

I coding-kategorien, Code Executor Mcp scorer 60.2/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Code Executor Mcp vs AutoGPT — Tillidsscore: 74.7/100
• Code Executor Mcp vs ollama — Tillidsscore: 73.8/100
• Code Executor Mcp vs langchain — Tillidsscore: 86.4/100

Vigtigste pointer

• Code Executor Mcp has a Tillidsscore of 60.2/100 (C) and is not yet Nerq Verified.
• Code Executor Mcp shows moderate trust signals. Conduct thorough due diligence before deploying to production environments.
• Among coding tools, Code Executor Mcp scores near the category average of 62/100, suggesting room for improvement relative to peers.
• Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.