Este Github Code sigur?
Github Code — Nerq Trust Score 56.9/100 (Nota D). Pe baza analizei a 1 dimensiuni de încredere, este are preocupări de securitate notabile. Ultima actualizare: 2026-04-06.
Folosiți Github Code cu precauție. Github Code este un software tool (codeparrot/github-code) cu un Scor de Încredere Nerq de 56.9/100 (D), based on 3 dimensiuni independente de date. Sub pragul verificat Nerq Date provenite din multiple surse publice inclusiv registre de pachete, GitHub, NVD, OSV.dev și OpenSSF Scorecard. Ultima actualizare: 2026-04-06. Date citibile de mașină (JSON).
Este Github Code sigur?
CAUTION — Github Code has a Nerq Trust Score of 56.9/100 (D). Are semnale de încredere moderat, dar prezintă unele zone de îngrijorare that warrant attention. Suitable for development use — review securitate and mentenanță signals before production deployment.
Care este scorul de încredere al Github Code?
Github Code are un Nerq Trust Score de 56.9/100 cu nota D. Acest scor se bazează pe 1 dimensiuni măsurate independent, inclusiv securitate, întreținere și adopție comunitară.
Care sunt principalele constatări de securitate pentru Github Code?
Cel mai puternic semnal al Github Code este conformitate la 87/100. Nu au fost detectate vulnerabilități cunoscute. It has not yet reached the Nerq Verified threshold of 70+.
Ce este Github Code și cine îl întreține?
| Autor | codeparrot |
| Categorie | Uncategorized |
| Stele | 353 |
| Sursă | https://huggingface.co/datasets/codeparrot/github-code |
| Protocols | huggingface_api |
Conformitate reglementară
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 87/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
What Is Github Code?
Github Code is a software tool in the uncategorized category: codeparrot/github-code. It has 353 GitHub stars. Nerq Trust Score: 57/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including securitate vulnerabilities, mentenanță activity, license conformitate, and adoptare comunitară.
How Nerq Assesses Github Code's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiuni. Here is how Github Code performs in each:
- Compliance (87/100): Github Code is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
The overall Trust Score of 56.9/100 (D) 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 Github Code?
Github Code is designed for:
- Developers and teams working with uncategorized tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Github Code is suitable for development and testing environments. Before production deployment, conduct a thorough review of its securitate posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Github Code's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Verificați repository securitate policy, open issues, and recent commits for signs of active mentenanță.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Github Code's dependency tree. - Recenzie permissions — Understand what access Github Code requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Github Code in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=github-code - Verificați license — Confirm that Github Code'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.
- 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 securitate concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Github Code
When evaluating whether Github Code is safe, consider these category-specific risks:
Understand how Github Code processes, stores, and transmits your data. Verificați tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Github Code's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher securitate risk.
Regularly check for updates to Github Code. Securitate patches and bug fixes are only effective if you're running the latest version.
If Github Code 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.
Verify that Github Code'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 Code in violation of its license can expose your organization to legal liability.
Best Practices for Using Github Code Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Github Code while minimizing risk:
Periodically review how Github Code is used in your workflow. Check for unexpected behavior, permissions drift, and conformitate with your securitate policies.
Ensure Github Code and all its dependencies are running the latest stable versions to benefit from securitate patches.
Grant Github Code only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Github Code's securitate advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Github Code is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Github Code?
Even promising tools aren't right for every situation. Consider avoiding Github Code in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional conformitate review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Github Code's trust score of 56.9/100 meets your organization's risk tolerance. We recommend running a manual securitate assessment alongside the automated Nerq score.
How Github Code 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. Github Code's score of 56.9/100 is near the category average of 62/100.
This places Github Code in line with the typical uncategorized 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 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 Github Code 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 mentenanță patterns change, Github Code'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 securitate and quality. Conversely, a downward trend may signal reduced mentenanță, growing technical debt, or unresolved vulnerabilities. To track Github Code's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=github-code&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 — securitate, mentenanță, documentație, conformitate, and community — has evolved independently, providing granular visibility into which aspects of Github Code are strengthening or weakening over time.
Concluzii principale
- Github Code has a Trust Score of 56.9/100 (D) and is not yet Nerq Verified.
- Github Code shows moderat trust signals. Conduct thorough due diligence before deploying to production environments.
- Among uncategorized tools, Github Code 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.
Întrebări frecvente
Este Github Code sigur?
Care este scorul de încredere al Github Code?
Care sunt alternative mai sigure la Github Code?
Cât de des este actualizat scorul de securitate al Github Code?
Pot folosi Github Code într-un mediu reglementat?
Vezi și
Disclaimer: Scorurile de încredere Nerq sunt evaluări automatizate bazate pe semnale disponibile public. Nu sunt recomandări sau garanții. Efectuați întotdeauna propria verificare.