Github Mcp Worker è sicuro?

Github Mcp Worker è sicuro?

Dettagli punteggio di fiducia — Github Mcp Worker has a Nerq Trust Score of 67.5/100 (C). Measured across 5 independent trust signals.

What Is Github Mcp Worker?

Github Mcp Worker is a software tool in the coding category: A read-only GitHub MCP server for Claude to browse public repos without access errors.. It has 1 GitHub stars. Nerq Trust Score: 68/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sicurezza vulnerabilities, manutenzione activity, license conformità, and adozione della comunità.

How Nerq Assesses Github Mcp Worker's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioni. Here is how Github Mcp Worker performs in each:

• Sicurezza (0/100): Github Mcp Worker's sicurezza posture is poor. This score factors in known CVEs, dependency vulnerabilities, sicurezza policy presence, and code signing practices.
• Manutenzione (1/100): Github Mcp Worker 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 documentazione, usage examples, and contribution guidelines.
• Compliance (100/100): Github Mcp Worker is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
• Community (0/100): Community adoption is limited. Basato su GitHub stars, forks, download counts, and ecosystem integrations.

The overall Trust Score of 67.5/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 Github Mcp Worker?

Github Mcp Worker is commonly evaluated by:

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

How to read the signals: Github Mcp Worker's measured signals (sicurezza 0/100, manutenzione 1/100, documentazione 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 Github Mcp Worker's Safety Yourself

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

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

Common Safety Concerns with Github Mcp Worker

When evaluating whether Github Mcp Worker is safe, consider these category-specific risks:

Github Mcp Worker and the EU AI Act

Github Mcp Worker 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 conformità assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal conformità.

Best Practices for Using Github Mcp Worker Safely

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

Situations That Warrant Independent Review of Github Mcp Worker

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

How Github Mcp Worker Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Trust Score is 62/100. Github Mcp Worker's score of 67.5/100 is above the category average of 62/100.

This positions Github Mcp Worker favorably among coding tools. While it outperforms the average, there is still room for improvement in certain trust dimensioni.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderato 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 Github Mcp Worker 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 manutenzione patterns change, Github Mcp Worker'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 sicurezza and quality. Conversely, a downward trend may signal reduced manutenzione, growing technical debt, or unresolved vulnerabilities. To track Github Mcp Worker's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=github-mcp-worker&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 — sicurezza, manutenzione, documentazione, conformità, and community — has evolved independently, providing granular visibility into which aspects of Github Mcp Worker are strengthening or weakening over time.

Github Mcp Worker vs Alternative

In the coding category, Github Mcp Worker scores 67.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Github Mcp Worker vs AutoGPT — Trust Score: 65.3/100
• Github Mcp Worker vs ollama — Trust Score: 64.4/100
• Github Mcp Worker vs langchain — Trust Score: 77.0/100

Punti chiave

• Github Mcp Worker has a measured Nerq Trust Score of 67.5/100 (C) — a composite of independent signals, not a suitability judgment.
• Among coding tools, Github Mcp Worker scores above the category average of 62/100 (a positional measurement relative to peers).
• The individual signals — sicurezza, manutenzione, documentazione, conformità, community — are shown above. Weigh them against your own requirements.
• Query the current measured values via Nerq's Preflight API.