Is Github Browser Skill veilig?

Is Github Browser Skill veilig?

Vertrouwensscore details — Github Browser Skill has a Nerq Trust Score of 54.5/100 (D). Measured across 5 independent trust signals.

What Is Github Browser Skill?

Github Browser Skill is a software tool in the coding category: Claude Code skill for efficient GitHub repo browsing with gh CLI.. Nerq Trust Score: 54/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.

How Nerq Assesses Github Browser Skill's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensies. Here is how Github Browser Skill performs in each:

• Beveiliging (0/100): Github Browser Skill's beveiliging posture is poor. This score factors in known CVEs, dependency vulnerabilities, beveiliging policy presence, and code signing practices.
• Onderhoud (1/100): Github Browser Skill 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 documentatie, usage examples, and contribution guidelines.
• Compliance (100/100): Github Browser Skill is broadly compliant. Assessed against regulations in 52 jurisdicties including the EU AI Act, CCPA, and GDPR.
• Community (0/100): Community adoption is limited. Gebaseerd op GitHub stars, forks, download counts, and ecosystem integrations.

The overall Trust Score of 54.5/100 (D) 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 Browser Skill?

Github Browser Skill 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 Browser Skill's measured signals (beveiliging 0/100, onderhoud 1/100, documentatie 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 Browser Skill's Safety Yourself

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

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

Common Safety Concerns with Github Browser Skill

When evaluating whether Github Browser Skill is safe, consider these category-specific risks:

Github Browser Skill and the EU AI Act

Github Browser Skill 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 naleving assessment covers 52 jurisdicties worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal naleving.

Best Practices for Using Github Browser Skill Safely

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

Situations That Warrant Independent Review of Github Browser Skill

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

How Github Browser Skill 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 Browser Skill's score of 54.5/100 is near the category average of 62/100.

This places Github Browser Skill 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 matig 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 Browser Skill 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 onderhoud patterns change, Github Browser Skill'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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, growing technical debt, or unresolved vulnerabilities. To track Github Browser Skill's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=github-browser-skill&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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Github Browser Skill are strengthening or weakening over time.

Github Browser Skill vs Alternatieven

In the coding category, Github Browser Skill scores 54.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Github Browser Skill vs AutoGPT — Trust Score: 65.3/100
• Github Browser Skill vs ollama — Trust Score: 64.4/100
• Github Browser Skill vs langchain — Trust Score: 77.0/100

Belangrijkste conclusies

• Github Browser Skill has a measured Nerq Trust Score of 54.5/100 (D) — a composite of independent signals, not a suitability judgment.
• Among coding tools, Github Browser Skill scores near the category average of 62/100 (a positional measurement relative to peers).
• The individual signals — beveiliging, onderhoud, documentatie, naleving, community — are shown above. Weigh them against your own requirements.
• Query the current measured values via Nerq's Preflight API.