Github Repository Creator è sicuro?
Github Repository Creator — Nerq Punteggio di fiducia 43.4/100 (Grado E). Sulla base dell'analisi di 3 dimensioni di fiducia, è ha preoccupazioni di sicurezza notevoli. Ultimo aggiornamento: 2026-03-31.
Fai attenzione con Github Repository Creator. Github Repository Creator is a software tool con un Punteggio di fiducia Nerq di 43.4/100 (E), based on 3 independent data dimensions. È al di sotto della soglia raccomandata di 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Dati leggibili dalle macchine (JSON).
Github Repository Creator è sicuro?
NO — USA CON CAUTELA — Github Repository Creator ha un Punteggio di fiducia Nerq di 43.4/100 (E). Ha segnali di fiducia inferiori alla media con lacune significative in sicurezza, manutenzione o documentazione. Non raccomandato per uso in produzione senza una revisione manuale accurata e misure di sicurezza aggiuntive.
Qual è il punteggio di fiducia di Github Repository Creator?
Github Repository Creator ha un Punteggio di fiducia Nerq di 43.4/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.
Quali sono i risultati di sicurezza chiave per Github Repository Creator?
Github Repository Creator's strongest signal is manutenzione at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
Cos'è Github Repository Creator e chi lo mantiene?
| Autore | https://github.com/flickleafy/mcp-github-repo-creator |
| Categoria | coding |
| Stelle | 2 |
| Fonte | https://github.com/flickleafy/mcp-github-repo-creator |
Alternative popolari in 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 Punteggio di fiducia: 43/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Github Repository Creator's Safety
Nerq's Punteggio di fiducia is calculated from 13+ independent signals aggregated into five dimensions. Here is how Github Repository Creator performs in each:
- Manutenzione (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. Based on GitHub stars, forks, download counts, and ecosystem integrations.
The overall Punteggio di fiducia 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 security, 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 — Review the repository security 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. - Recensione 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 - Controlla 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 security 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. Review the 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 security risk.
Regularly check for updates to Github Repository Creator. Security 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 compliance with your security policies.
Ensure Github Repository Creator and all its dependencies are running the latest stable versions to benefit from security 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 security 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 compliance review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Github Repository Creator pari a 43.4/100 meets your organization's risk tolerance. We recommend running a manual security 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 Punteggio di fiducia 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 security 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 moderate 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.
Punteggio di fiducia History
Nerq continuously monitors Github Repository Creator and recalculates its Punteggio di fiducia 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 security 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 — security, maintenance, documentation, compliance, 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
Nella categoria coding, Github Repository Creator ottiene 43.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Github Repository Creator vs AutoGPT — Punteggio di fiducia: 74.7/100
- Github Repository Creator vs ollama — Punteggio di fiducia: 73.8/100
- Github Repository Creator vs langchain — Punteggio di fiducia: 86.4/100
Punti chiave
- Github Repository Creator has a Punteggio di fiducia of 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.
Domande frequenti
Github Repository Creator è sicuro da usare?
Cos'è Github Repository Creator's trust score?
Quali sono le alternative più sicure a Github Repository Creator?
How often is Github Repository Creator's safety score updated?
Posso usare Github Repository Creator in un ambiente regolamentato?
Disclaimer: I punteggi di fiducia Nerq sono valutazioni automatizzate basate su segnali disponibili pubblicamente. Non costituiscono raccomandazioni o garanzie. Effettua sempre la tua verifica personale.