هل Github Browser Skill آمن؟

Github Browser Skill — Nerq درجة الثقة 54.5/100 (الدرجة D). التقييم مبني على 5 independent trust signals.

Github Browser Skill هو software tool بدرجة ثقة Nerq 54.5/100 (D), بناءً على 5 أبعاد بيانات مستقلة. الأمان: 0/100. الصيانة: 1/100. الشعبية: 0/100. البيانات مصدرها قراءة آلية.

هل Github Browser Skill آمن؟

تفاصيل درجة الثقة — Github Browser Skill لديه درجة ثقة Nerq تبلغ 54.5/100 (D). Measured across 5 independent trust signals.

تحليل الأمان → تقرير الخصوصية →

ما هي درجة ثقة Github Browser Skill؟

حصل Github Browser Skill على درجة ثقة Nerq تبلغ 54.5/100 بدرجة D. يعتمد هذا التقييم على 5 أبعاد مُقاسة بشكل مستقل.

الأمان
0
الامتثال
100
الصيانة
1
التوثيق
1
الشعبية
0

ما هي النتائج الأمنية الرئيسية لـ Github Browser Skill؟

أقوى إشارة لـ Github Browser Skill هي الامتثال بدرجة 100/100. لم يتم اكتشاف أي ثغرات أمنية معروفة.

⚠درجة الأمان: 0/100 (ضعيف)
⚠الصيانة: 1/100 — نشاط صيانة منخفض
⚠الامتثال: 100/100 — covers 52 of 52 ولاية قضائيةs
⚠التوثيق: 1/100 — توثيق محدود
⚠الشعبية: 0/100 — اعتماد المجتمع

ما هو Github Browser Skill ومن يديره؟

المؤلفbotingw
الفئةCoding
المصدرhttps://github.com/botingw/github-browser-skill
Frameworksanthropic
Protocolsrest

الامتثال التنظيمي

EU AI Act Risk ClassMINIMAL
Compliance Score100/100
الاختصاص القضائيsAssessed across 52 ولاية قضائيةs

بدائل شائعة في coding

Significant-Gravitas/AutoGPT
65.3/100 · C
github
ollama/ollama
64.4/100 · C
github
langchain-ai/langchain
77.0/100 · B
github
x1xhlol/system-prompts-and-models-of-ai-tools
64.4/100 · C
github
anomalyco/opencode
78.5/100 · B
github

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 درجة الثقة: 54/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and اعتماد المجتمع.

How Nerq Assesses Github Browser Skill's Safety

Nerq's درجة الثقة is calculated from 13+ independent signals aggregated into five أبعاد. Here is how Github Browser Skill performs in each:

The overall درجة الثقة 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:

كيفية read the signals: Github Browser Skill's measured signals (security 0/100, maintenance 1/100, documentation 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.

كيفية 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 — Review the repository's 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 ثغرات أمنية معروفة in Github Browser Skill's dependency tree.
  3. مراجعة 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. مراجعة the 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 عملاء 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 Github Browser Skill

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

Data handling

Understand how Github Browser Skill processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Github Browser Skill's dependency tree for ثغرات أمنية معروفة. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Github Browser Skill. الأمان patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Github Browser Skill 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.

الترخيص and IP compliance

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

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 compliance assessment covers 52 ولاية قضائيةs worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.

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:

Conduct regular audits

Periodically review how Github Browser Skill is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Github Browser Skill and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

Grant Github Browser Skill only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for security advisories

Subscribe to Github Browser Skill's security 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 Github Browser Skill is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant مستقل 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:

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 درجة الثقة 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 متوسط 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.

درجة الثقة History

Nerq continuously monitors Github Browser Skill and recalculates its درجة الثقة 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, 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 security and quality. Conversely, a downward trend may signal reduced maintenance, 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 — security, maintenance, documentation, compliance, 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 البدائل

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 آمن؟
github-browser-skill بدرجة ثقة Nerq 54.5/100 (D). أقوى إشارة: الامتثال (100/100). التقييم مبني على الأمان (0/100), الصيانة (1/100), الشعبية (0/100), التوثيق (1/100).
ما هي درجة ثقة Github Browser Skill؟
github-browser-skill: 54.5/100 (D). التقييم مبني على الأمان (0/100), الصيانة (1/100), الشعبية (0/100), التوثيق (1/100). Compliance: 100/100. يتم تحديث النتائج عند توفر بيانات جديدة. API: GET nerq.ai/v1/preflight?target=github-browser-skill
ما هي البدائل الأكثر أمانًا لـ Github Browser Skill؟
في فئة Coding، البدائل الأعلى تقييمًا تشمل Significant-Gravitas/AutoGPT (65/100), ollama/ollama (64/100), langchain-ai/langchain (77/100). github-browser-skill scores 54.5/100.
كم مرة يتم تحديث درجة أمان Github Browser Skill؟
Nerq recomputes Github Browser Skill's trust score as new data becomes available. Current: 54.5/100 (D). API: GET nerq.ai/v1/preflight?target=github-browser-skill
هل يمكنني استخدام Github Browser Skill في بيئة منظمة؟
Github Browser Skill: 54.5/100 (D). Compliance: 52 of 52 ولاية قضائيةs. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge واجهة برمجة التطبيقات Docs

انظر أيضاً

إخلاء المسؤولية: درجات ثقة Nerq هي تقييمات آلية مبنية على إشارات متاحة للعموم. وهي ليست توصيات أو ضمانات. قم دائمًا بإجراء العناية الواجبة الخاصة بك.

نستخدم ملفات تعريف الارتباط للتحليلات والتخزين المؤقت. الخصوصية