Czy Github Integration Hub jest bezpieczny?
Github Integration Hub — Nerq Wynik zaufania 40.0/100 (Ocena E). Na podstawie analizy 3 wymiarów zaufania, jest ma istotne obawy dotyczące bezpieczeństwa. Ostatnia aktualizacja: 2026-04-02.
Zachowaj ostrożność z Github Integration Hub. Github Integration Hub is a software tool with a Nerq Wynik zaufania of 40.0/100 (E), based on 3 niezależnych wymiarów danych. Jest poniżej zalecanego progu wynoszącego 70. Konserwacja: 0/100. Popularity: 0/100. Dane pochodzą z multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Ostatnia aktualizacja: 2026-04-02. Dane odczytywalne maszynowo (JSON).
Czy Github Integration Hub jest bezpieczny?
NIE — UŻYWAJ Z OSTROŻNOŚCIĄ — Github Integration Hub has a Nerq Wynik zaufania of 40.0/100 (E). Ma poniżej przeciętne sygnały zaufania ze znaczącymi lukami w zakresie bezpieczeństwa, konserwacji lub dokumentacji. Niezalecany do użytku produkcyjnego bez dokładnego ręcznego przeglądu i dodatkowych środków bezpieczeństwa.
Jaki jest wynik zaufania Github Integration Hub?
Github Integration Hub has a Nerq Wynik zaufania of 40.0/100, earning a E grade. This score is based on 3 independently measured wymiarów including bezpieczeństwo, konserwacja, and przyjęcie przez społeczność.
Jakie są kluczowe ustalenia bezpieczeństwa dla Github Integration Hub?
Github Integration Hub's strongest signal is konserwacja at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
Czym jest Github Integration Hub i kto go utrzymuje?
| Autor | https://github.com/crbatista/mcp-cli-github-integration |
| Kategoria | infrastructure |
| Gwiazdki | 1 |
| Źródło | https://github.com/crbatista/mcp-cli-github-integration |
Popularne alternatywy w infrastructure
What Is Github Integration Hub?
Github Integration Hub is a software tool in the infrastructure category: Provides GitHub OAuth authentication and API access through REST endpoints, CLI tools, and MCP server capabilities with SQLite-based token storage.. It has 1 GitHub stars. Nerq Wynik zaufania: 40/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.
How Nerq Assesses Github Integration Hub's Safety
Nerq's Wynik zaufania is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Github Integration Hub performs in each:
- Konserwacja (0/100): Github Integration Hub 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 dokumentacja, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Na podstawie GitHub stars, forks, download counts, and ecosystem integrations.
The overall Wynik zaufania of 40.0/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 Integration Hub?
Github Integration Hub is designed for:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Github Integration Hub. The low trust score suggests potential risks in bezpieczeństwo, konserwacja, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Github Integration Hub's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Sprawdź repository bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Github Integration Hub's dependency tree. - Opinia permissions — Understand what access Github Integration Hub requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Github Integration Hub 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 Integration Hub - Sprawdź license — Confirm that Github Integration Hub'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 bezpieczeństwo concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Github Integration Hub
When evaluating whether Github Integration Hub is safe, consider these category-specific risks:
Understand how Github Integration Hub processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Github Integration Hub's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.
Regularly check for updates to Github Integration Hub. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.
If Github Integration Hub 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 Integration Hub'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 Integration Hub in violation of its license can expose your organization to legal liability.
Best Practices for Using Github Integration Hub Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Github Integration Hub while minimizing risk:
Periodically review how Github Integration Hub is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.
Ensure Github Integration Hub and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.
Grant Github Integration Hub only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Github Integration Hub's bezpieczeństwo advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Github Integration Hub is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Github Integration Hub?
Even promising tools aren't right for every situation. Consider avoiding Github Integration Hub in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional zgodność review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Github Integration Hub 40.0/100 meets your organization's risk tolerance. We recommend running a manual bezpieczeństwo assessment alongside the automated Nerq score.
How Github Integration Hub Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Wynik zaufania is 62/100. Github Integration Hub's score of 40.0/100 is below the category average of 62/100.
This suggests that Github Integration Hub trails behind many comparable infrastructure tools. Organizations with strict bezpieczeństwo 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 umiarkowany 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.
Wynik zaufania History
Nerq continuously monitors Github Integration Hub and recalculates its Wynik zaufania 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 konserwacja patterns change, Github Integration Hub'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 bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, growing technical debt, or unresolved vulnerabilities. To track Github Integration Hub's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GitHub Integration Hub&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 — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Github Integration Hub are strengthening or weakening over time.
Github Integration Hub vs Alternatywy
W kategorii infrastructure, Github Integration Hub uzyskuje 40.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Github Integration Hub vs n8n — Wynik zaufania: 78.5/100
- Github Integration Hub vs langflow — Wynik zaufania: 87.6/100
- Github Integration Hub vs dify — Wynik zaufania: 79.1/100
Kluczowe wnioski
- Github Integration Hub has a Wynik zaufania of 40.0/100 (E) and is not yet Nerq Verified.
- Github Integration Hub has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among infrastructure tools, Github Integration Hub 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.
Często zadawane pytania
Czy Github Integration Hub jest bezpieczny w użyciu?
Czym jest Github Integration Hub's trust score?
Jakie są bezpieczniejsze alternatywy dla Github Integration Hub?
How often is Github Integration Hub's safety score updated?
Czy mogę używać Github Integration Hub w środowisku regulowanym?
Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.