Czy Github Integration Hub jest bezpieczny?

Github Integration Hub — Nerq Trust Score 40.0/100 (Ocena E). Na podstawie analizy 3 wymiarów zaufania, jest ma istotne obawy dotyczące bezpieczeństwa. Ostatnia aktualizacja: 2026-04-10.

Zachowaj ostrożność z Github Integration Hub. Github Integration Hub to software tool z wynikiem zaufania Nerq 40.0/100 (E), based on 3 niezależnych wymiarów danych. Poniżej zweryfikowanego progu Nerq Konserwacja: 0/100. Popularność: 0/100. Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: 2026-04-10. Dane odczytywalne maszynowo (JSON).

Czy Github Integration Hub jest bezpieczny?

NO — USE WITH CAUTION — Github Integration Hub has a Nerq Trust Score of 40.0/100 (E). Ma poniżej przeciętne sygnały zaufania ze znaczącymi lukami in bezpieczeństwo, konserwacja, or dokumentacja. Not recommended for production use without thorough manual review and additional bezpieczeństwo measures.

Analiza bezpieczeństwa → Raport prywatności Github Integration Hub →

Jaki jest wynik zaufania Github Integration Hub?

Github Integration Hub ma Nerq Trust Score 40.0/100 z oceną E. Ten wynik opiera się na 3 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.

Konserwacja
0
Dokumentacja
0
Popularność
0

Jakie są kluczowe ustalenia bezpieczeństwa dla Github Integration Hub?

Najsilniejszy sygnał Github Integration Hub to konserwacja na poziomie 0/100. Nie wykryto znanych luk w zabezpieczeniach. It has not yet reached the Nerq Verified threshold of 70+.

Konserwacja: 0/100 — niska aktywność konserwacji
Dokumentacja: 0/100 — ograniczona dokumentacja
Popularność: 0/100 — 1 gwiazdek na pulsemcp

Czym jest Github Integration Hub i kto go utrzymuje?

Autorhttps://github.com/crbatista/mcp-cli-github-integration
KategoriaInfrastructure
Gwiazdki1
Źródłohttps://github.com/crbatista/mcp-cli-github-integration

Popularne alternatywy w infrastructure

n8n-io/n8n
78.5/100 · B
github
langflow-ai/langflow
87.6/100 · A
github
langgenius/dify
79.1/100 · B
github
open-webui/open-webui
74.8/100 · B
github
google-gemini/gemini-cli
71.8/100 · B
github

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 Trust Score: 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 Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Github Integration Hub performs in each:

The overall Trust Score 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:

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:

  1. Check the source code — Sprawdź repository bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Github Integration Hub's dependency tree.
  3. Opinia permissions — Understand what access Github Integration Hub requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Github Integration Hub 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 Integration Hub
  6. 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.
  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 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:

Data handling

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.

Dependency bezpieczeństwo

Check Github Integration Hub's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.

Update frequency

Regularly check for updates to Github Integration Hub. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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.

License and IP zgodność

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:

Conduct regular audits

Periodically review how Github Integration Hub is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.

Keep dependencies updated

Ensure Github Integration Hub and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.

Follow least privilege

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

Monitor for bezpieczeństwo advisories

Subscribe to Github Integration Hub's bezpieczeństwo 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 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:

For each scenario, evaluate whether Github Integration Hub's trust score of 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 Trust Score 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.

Trust Score History

Nerq continuously monitors Github Integration Hub 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 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

In the infrastructure category, Github Integration Hub scores 40.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Kluczowe wnioski

Często zadawane pytania

Czy Github Integration Hub jest bezpieczny?
Zachowaj ostrożność. GitHub Integration Hub z wynikiem zaufania Nerq 40.0/100 (E). Najsilniejszy sygnał: konserwacja (0/100). Wynik oparty na Konserwacja (0/100), Popularność (0/100), Dokumentacja (0/100).
Jaki jest wynik zaufania Github Integration Hub?
GitHub Integration Hub: 40.0/100 (E). Wynik oparty na Konserwacja (0/100), Popularność (0/100), Dokumentacja (0/100). Oceny aktualizują się, gdy pojawiają się nowe dane. API: GET nerq.ai/v1/preflight?target=GitHub Integration Hub
Jakie są bezpieczniejsze alternatywy dla Github Integration Hub?
W kategorii Infrastructure, higher-rated alternatives include n8n-io/n8n (78/100), langflow-ai/langflow (88/100), langgenius/dify (79/100). GitHub Integration Hub scores 40.0/100.
Jak często aktualizowana jest ocena bezpieczeństwa Github Integration Hub?
Nerq continuously monitors Github Integration Hub and updates its trust score as new data becomes available. Current: 40.0/100 (E), last zweryfikowane 2026-04-10. API: GET nerq.ai/v1/preflight?target=GitHub Integration Hub
Czy mogę używać Github Integration Hub w środowisku regulowanym?
Github Integration Hub nie osiągnął progu weryfikacji Nerq 70. Zalecana dodatkowa weryfikacja.
API: /v1/preflight Trust Badge API Docs

Zobacz także

Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.

Używamy plików cookie do analiz i buforowania. Prywatność