Github Repository Creator est-il sûr ?
Github Repository Creator — Nerq Trust Score 43.4/100 (Note E). Sur la base de l'analyse de 3 dimensions de confiance, il est a des préoccupations de sécurité notables. Dernière mise à jour : 2026-04-02.
Faites preuve de prudence avec Github Repository Creator. Github Repository Creator is a software tool avec un Score de Confiance Nerq de 43.4/100 (E), based on 3 dimensions de données indépendantes. It is below the recommended threshold of 70. Maintenance: 0/100. Popularity: 0/100. Données provenant de multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Dernière mise à jour: 2026-04-02. Données lisibles par machine (JSON).
Github Repository Creator est-il sûr ?
NO — USE WITH CAUTION — Github Repository Creator a un Score de Confiance Nerq de 43.4/100 (E). Il présente des signaux de confiance inférieurs à la moyenne avec des lacunes significatives in sécurité, maintenance, or documentation. Not recommended for production use without thorough manual review and additional sécurité measures.
Quel est le score de confiance de Github Repository Creator ?
Github Repository Creator a un Score de Confiance Nerq de 43.4/100, obtenant la note E. Ce score est basé sur 3 dimensions mesurées indépendamment.
Quels sont les résultats de sécurité clés pour Github Repository Creator ?
Le signal le plus fort de Github Repository Creator est maintenance à 0/100. Aucune vulnérabilité connue n'a été détectée. N'a pas encore atteint le seuil vérifié Nerq de 70+.
Qu'est-ce que Github Repository Creator et qui le maintient ?
| Auteur | https://github.com/flickleafy/mcp-github-repo-creator |
| Catégorie | coding |
| Étoiles | 2 |
| Source | https://github.com/flickleafy/mcp-github-repo-creator |
Alternatives populaires dans coding
What Is Github Repository Creator?
Github Repository Creator is a software tool in the coding category: Automates GitHub repository creation based on local codebase analysis.. It has 2 GitHub stars. Nerq Trust Score: 43/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sécurité vulnerabilities, maintenance activity, license conformité, and adoption par la communauté.
How Nerq Assesses Github Repository Creator's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Github Repository Creator performs in each:
- Maintenance (0/100): Github Repository Creator is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Basé sur GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 43.4/100 (E) 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 Repository Creator?
Github Repository Creator 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: We recommend caution with Github Repository Creator. The low trust score suggests potential risks in sécurité, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Github Repository Creator's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Examiner le/la repository sécurité policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Github Repository Creator's dependency tree. - Avis permissions — Understand what access Github Repository Creator requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Github Repository Creator 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 Repository Creator - Examiner le/la license — Confirm that Github Repository Creator'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Github Repository Creator
When evaluating whether Github Repository Creator is safe, consider these category-specific risks:
Understand how Github Repository Creator processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Github Repository Creator's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.
Regularly check for updates to Github Repository Creator. Sécurité patches and bug fixes are only effective if you're running the latest version.
If Github Repository Creator 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 Repository Creator'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 Repository Creator in violation of its license can expose your organization to legal liability.
Best Practices for Using Github Repository Creator Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Github Repository Creator while minimizing risk:
Periodically review how Github Repository Creator is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.
Ensure Github Repository Creator and all its dependencies are running the latest stable versions to benefit from sécurité patches.
Grant Github Repository Creator only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Github Repository Creator's sécurité advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Github Repository Creator is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Github Repository Creator?
Even promising tools aren't right for every situation. Consider avoiding Github Repository Creator in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional conformité review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Github Repository Creator de 43.4/100 meets your organization's risk tolerance. We recommend running a manual sécurité assessment alongside the automated Nerq score.
How Github Repository Creator 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 Repository Creator's score of 43.4/100 is below the category average of 62/100.
This suggests that Github Repository Creator trails behind many comparable coding tools. Organizations with strict sécurité requirements should evaluate whether higher-scoring alternatives better meet their needs.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks modéré 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 Repository Creator 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 maintenance patterns change, Github Repository Creator'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 sécurité and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Github Repository Creator's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GitHub Repository Creator&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 — sécurité, maintenance, documentation, conformité, and community — has evolved independently, providing granular visibility into which aspects of Github Repository Creator are strengthening or weakening over time.
Github Repository Creator vs Alternatives
In the coding category, Github Repository Creator scores 43.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Github Repository Creator vs AutoGPT — Trust Score: 74.7/100
- Github Repository Creator vs ollama — Trust Score: 73.8/100
- Github Repository Creator vs langchain — Trust Score: 86.4/100
Points Essentiels
- Github Repository Creator a un Score de Confiance de 43.4/100 (E) and is not yet Nerq Verified.
- Github Repository Creator has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among coding tools, Github Repository Creator scores below 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.
Questions fréquentes
Est-ce que Github Repository Creator sûr à utiliser?
Qu'est-ce que Github Repository Creator's trust score ?
Quelles sont les alternatives plus sûres à Github Repository Creator ?
How often is Github Repository Creator's safety score updated?
Can I use Github Repository Creator in a regulated environment?
Disclaimer: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.