Github Chat安全吗?

Github Chat — Nerq Trust Score 58.1/100 (D级). 基于5 independent trust signals的评分。

Github Chat 是一个software tool Nerq 信任分数 58.1/100(D), 基于5个独立数据维度. 安全: 0/100. 维护: 0/100. 人气度: 0/100. 数据来源于多个公共来源,包括包注册表、GitHub、NVD、OSV.dev和OpenSSF Scorecard。最后更新:n/a。 机器可读数据(JSON).

Github Chat安全吗?

信任评分详情 — Github Chat has a Nerq Trust Score of 58.1/100 (D). Measured across 5 independent trust signals.

安全分析 → Github Chat隐私报告 →

Github Chat的信任评分是多少?

Github Chat 的 Nerq 信任分数为 58.1/100,等级为 D。该分数基于 5 个独立测量的维度,包括安全性、维护和社区采用。

安全性
0
合规性
82
维护
0
文档
0
人气
0

Github Chat的主要安全发现是什么?

Github Chat 最强的信号是 合规性,为 82/100。 未检测到已知漏洞。

⚠安全评分: 0/100 (弱)
⚠维护: 0/100 — 低维护活动
⚠合规性: 82/100 — covers 42 of 52 司法管辖区s
⚠文档: 0/100 — 有限文档
⚠人气: 0/100 — 4 在以下平台的星标 docker hub

Github Chat是什么,谁在维护它?

开发者mcp
类别基础设施
星标4
来源https://hub.docker.com/r/mcp/github-chat
Protocolsdocker

合规性

EU AI Act Risk ClassMINIMAL
Compliance Score82/100
管辖权sAssessed across 52 司法管辖区s

infrastructure中的热门替代品

n8n-io/n8n
69.1/100 · C
github
langflow-ai/langflow
77.0/100 · B
github
langgenius/dify
69.7/100 · C
github
open-webui/open-webui
60.4/100 · C
github
google-gemini/gemini-cli
56.2/100 · D
github

What Is Github Chat?

Github Chat is a software tool in the infrastructure category: A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Ch.... It has 4 GitHub stars. Nerq Trust Score: 58/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including 安全性 vulnerabilities, 维护 activity, license 合规性, and 社区采用.

How Nerq Assesses Github Chat's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 维度. Here is how Github Chat performs in each:

The overall Trust Score of 58.1/100 (D) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.

Who Typically Evaluates Github Chat?

Github Chat is commonly evaluated by:

How to read the signals: Github Chat's measured signals (安全性 0/100, 维护 0/100, 文档 0/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.

How to Verify Github Chat's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — 查看 repository 安全性 policy, open issues, and recent commits for signs of active 维护.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Github Chat's dependency tree.
  3. 评论 permissions — Understand what access Github Chat requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Github Chat 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-chat
  6. 查看 license — Confirm that Github Chat'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 安全性 concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Github Chat

When evaluating whether Github Chat is safe, consider these category-specific risks:

Data handling

Understand how Github Chat processes, stores, and transmits your data. 查看 tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency 安全性

Check Github Chat's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher 安全性 risk.

Update frequency

Regularly check for updates to Github Chat. 安全性 patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Github Chat 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 合规性

Verify that Github Chat'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 Chat in violation of its license can expose your organization to legal liability.

Github Chat and the EU AI Act

Github Chat is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.

Nerq's 合规性 assessment covers 52 司法管辖区s worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal 合规性.

Best Practices for Using Github Chat Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Github Chat while minimizing risk:

Conduct regular audits

Periodically review how Github Chat is used in your workflow. Check for unexpected behavior, permissions drift, and 合规性 with your 安全性 policies.

Keep dependencies updated

Ensure Github Chat and all its dependencies are running the latest stable versions to benefit from 安全性 patches.

Follow least privilege

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

Monitor for 安全性 advisories

Subscribe to Github Chat's 安全性 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 Chat is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant 独立 Review of Github Chat

Nerq's signals are one input. In the following situations, evaluate Github Chat's measured signals against your own requirements before making a decision:

For each situation, compare Github Chat's measured trust score of 58.1/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Github Chat is suitable for any particular use.

How Github Chat 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 Chat's score of 58.1/100 is near the category average of 62/100.

This places Github Chat in line with the typical infrastructure 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 中等 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 Chat 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 维护 patterns change, Github Chat'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 安全性 and quality. Conversely, a downward trend may signal reduced 维护, growing technical debt, or unresolved vulnerabilities. To track Github Chat's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=github-chat&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 — 安全性, 维护, 文档, 合规性, and community — has evolved independently, providing granular visibility into which aspects of Github Chat are strengthening or weakening over time.

Github Chat vs 替代品

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

主要结论

常见问题

Github Chat安全吗?
github-chat Nerq 信任分数 58.1/100(D). 最强信号: 合规性 (82/100). 基于安全 (0/100), 维护 (0/100), 人气度 (0/100), 文档 (0/100)的评分。
Github Chat的信任评分是多少?
github-chat: 58.1/100 (D). 基于安全 (0/100), 维护 (0/100), 人气度 (0/100), 文档 (0/100)的评分。 Compliance: 82/100. 新数据可用时分数会更新. API: GET nerq.ai/v1/preflight?target=github-chat
Github Chat有哪些更安全的替代品?
在基础设施类别中, higher-rated alternatives include n8n-io/n8n (69/100), langflow-ai/langflow (77/100), langgenius/dify (70/100). github-chat scores 58.1/100.
Github Chat的安全评分多久更新一次?
Nerq recomputes Github Chat's trust score as new data becomes available. Current: 58.1/100 (D). API: GET nerq.ai/v1/preflight?target=github-chat
我可以在受监管的环境中使用Github Chat吗?
Github Chat: 58.1/100 (D). Compliance: 42 of 52 司法管辖区s. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

另请参阅

Disclaimer: Nerq 信任评分是基于公开信号的自动评估。它们不构成建议或保证。请始终进行自己的验证。

我们使用Cookie进行分析和缓存。 隐私