Github Agentic Chat安全吗?
Github Agentic Chat — Nerq 信任评分 39.8/100 (E级). 基于5个信任维度的分析,被评估为存在重大安全风险。 最后更新:2026-04-03。
请对Github Agentic Chat保持警惕。 Github Agentic Chat is a software tool Nerq 信任评分为 39.8/100 (E). 低于推荐阈值 70。 数据来源于 multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. 最后更新: 2026-04-03. 机器可读数据(JSON).
Github Agentic Chat安全吗?
否——请谨慎使用 — Github Agentic Chat Nerq 信任评分为 39.8/100 (E). 信任信号低于平均水平,在安全性、维护或文档方面存在重大缺口. 未经彻底手动审查和额外安全措施,不建议用于生产环境.
Github Agentic Chat的信任评分是多少?
Github Agentic Chat Nerq 信任评分为 39.8/100, earning a E grade. This score is based on 5 independently measured 维度 including 安全性, 维护, and 社区采用.
Github Agentic Chat的主要安全发现是什么?
Github Agentic Chat's strongest signal is 整体信任度 at 39.8/100. No 已知漏洞 have been detected. It has not yet reached the Nerq Verified threshold of 70+.
Github Agentic Chat是什么,谁在维护它?
| 开发者 | https://github.com/akhidastech/github-agentic-chat-mcp |
| 类别 | uncategorized |
| 来源 | https://github.com/akhidastech/github-agentic-chat-mcp |
What Is Github Agentic Chat?
Github Agentic Chat is a software tool in the uncategorized category: Integrates with GitHub's API to enable natural language interaction with repositories, offering tools for searching, creating issues, and performing semantic searches across stored documents using PostgreSQL with pgvector.. Nerq 信任评分: 40/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including 安全性 vulnerabilities, 维护 activity, license 合规性, and 社区采用.
How Nerq Assesses Github Agentic Chat's Safety
Nerq evaluates every software tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core 维度: 安全性 (known CVEs, dependency vulnerabilities, 安全性 policies), 维护 (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 司法管辖区s), and Community (stars, forks, downloads, ecosystem integrations).
Github Agentic Chat receives an overall 信任评分 of 39.8/100 (E), which Nerq considers low. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.
Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=GitHub Agentic Chat
Each dimension is weighted according to its importance for the tool's category. For example, 安全性 and 维护 carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Github Agentic Chat's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five 维度, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).
Who Should Use Github Agentic Chat?
Github Agentic Chat is designed for:
- Developers and teams working with uncategorized tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Github Agentic Chat. The low trust score suggests potential risks in 安全性, 维护, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Github Agentic Chat's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — 查看 repository 安全性 policy, open issues, and recent commits for signs of active 维护.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for 已知漏洞 in Github Agentic Chat's dependency tree. - 评论 permissions — Understand what access Github Agentic Chat requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Github Agentic Chat 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 Agentic Chat - 查看 license — Confirm that Github Agentic 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.
- 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 Agentic Chat
When evaluating whether Github Agentic Chat is safe, consider these category-specific risks:
Understand how Github Agentic Chat processes, stores, and transmits your data. 查看 tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Github Agentic Chat's dependency tree for 已知漏洞. Tools with outdated or unmaintained dependencies pose a higher 安全性 risk.
Regularly check for updates to Github Agentic Chat. 安全性 patches and bug fixes are only effective if you're running the latest version.
If Github Agentic 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.
Verify that Github Agentic 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 Agentic Chat in violation of its license can expose your organization to legal liability.
Best Practices for Using Github Agentic Chat Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Github Agentic Chat while minimizing risk:
Periodically review how Github Agentic Chat is used in your workflow. Check for unexpected behavior, permissions drift, and 合规性 with your 安全性 policies.
Ensure Github Agentic Chat and all its dependencies are running the latest stable versions to benefit from 安全性 patches.
Grant Github Agentic Chat only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Github Agentic Chat's 安全性 advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Github Agentic Chat is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Github Agentic Chat?
Even promising tools aren't right for every situation. Consider avoiding Github Agentic Chat in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional 合规性 review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Github Agentic Chat的信任评分为 39.8/100 meets your organization's risk tolerance. We recommend running a manual 安全性 assessment alongside the automated Nerq score.
How Github Agentic Chat Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average 信任评分 is 62/100. Github Agentic Chat's score of 39.8/100 is below the category average of 62/100.
This suggests that Github Agentic Chat trails behind many comparable uncategorized tools. Organizations with strict 安全性 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 中等 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.
信任评分 History
Nerq continuously monitors Github Agentic Chat and recalculates its 信任评分 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 Agentic 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 Agentic Chat's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GitHub Agentic 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 Agentic Chat are strengthening or weakening over time.
主要结论
- Github Agentic Chat has a 信任评分 of 39.8/100 (E) and is not yet Nerq Verified.
- Github Agentic Chat has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among uncategorized tools, Github Agentic Chat 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.
常见问题
Github Agentic Chat可以安全使用吗?
Github Agentic Chat's trust score是什么?
Github Agentic Chat有哪些更安全的替代品?
How often is Github Agentic Chat's safety score updated?
我可以在受监管环境中使用Github Agentic Chat吗?
Disclaimer: Nerq 信任评分是基于公开信号的自动评估。它们不构成建议或保证。请始终进行自己的验证。