Gogogotは安全ですか?
Gogogot — Nerq Trust Score 52.1/100 (Dグレード). スコアの基準: 4 independent trust signals.
Gogogot はsoftware toolです Nerq信頼スコア52.1/100(D), 4つの独立したデータ次元に基づく. セキュリティ: 0/100. メンテナンス: 1/100. 人気度: 1/100. データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. 最終更新: n/a. 機械可読データ(JSON).
Gogogotは安全ですか?
信頼スコアの内訳 — Gogogot has a Nerq Trust Score of 52.1/100 (D). Measured across 4 independent trust signals.
Gogogotの信頼スコアは?
GogogotのNerq信頼スコアは52.1/100で、Dグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む4の独立した次元に基づいています。
Gogogotの主なセキュリティ調査結果は?
Gogogotの最も強いシグナルはメンテナンスで1/100です。 既知の脆弱性は検出されていません。
Gogogotとは何で、誰が管理していますか?
| 作者 | aspasskiy |
| カテゴリ | Agent |
| Stars | 382 |
| Source | https://github.com/aspasskiy/GoGogot |
| Frameworks | openai · anthropic |
| Protocols | rest |
agentの人気の代替品
What Is Gogogot?
Gogogot is a software tool in the agent category: GoGogot is a lightweight self-hosted AI agent in Go.. It has 382 GitHubスター. Nerq Trust Score: 52/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.
How Nerq Assesses Gogogot's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 次元. Here is how Gogogot performs in each:
- セキュリティ (0/100): Gogogot's セキュリティ posture is poor. This score factors in known CVEs, dependency vulnerabilities, セキュリティ policy presence, and code signing practices.
- メンテナンス (1/100): Gogogot is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API ドキュメント, usage examples, and contribution guidelines.
- Community (1/100): Community adoption is limited. に基づく GitHubスター, forks, download counts, and ecosystem integrations.
The overall Trust Score of 52.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 Gogogot?
Gogogot is commonly evaluated by:
- Developers and teams working with agent tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Gogogot's measured signals (セキュリティ 0/100, メンテナンス 1/100, ドキュメント 1/100, community 1/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 Gogogot's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — 確認してください repository's セキュリティ policy, open issues, and recent commits for signs of active メンテナンス.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Gogogot's dependency tree. - レビュー permissions — Understand what access Gogogot requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Gogogot 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=GoGogot - 確認してください license — Confirm that Gogogot'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 Gogogot
When evaluating whether Gogogot is safe, consider these category-specific risks:
Understand how Gogogot processes, stores, and transmits your data. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Gogogot's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.
Regularly check for updates to Gogogot. セキュリティ patches and bug fixes are only effective if you're running the latest version.
If Gogogot 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 Gogogot's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Gogogot in violation of its license can expose your organization to legal liability.
Best Practices for Using Gogogot Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Gogogot while minimizing risk:
Periodically review how Gogogot is used in your workflow. Check for unexpected behavior, permissions drift, and コンプライアンス with your セキュリティ policies.
Ensure Gogogot and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.
Grant Gogogot only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Gogogot's セキュリティ advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Gogogot is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Gogogot
Nerq's signals are one input. In the following situations, evaluate Gogogot's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Gogogot's measured trust score of 52.1/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Gogogot is suitable for any particular use.
How Gogogot Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among agent tools, the average Trust Score is 62/100. Gogogot's score of 52.1/100 is near the category average of 62/100.
This places Gogogot in line with the typical agent 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 Gogogot 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, Gogogot'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 Gogogot's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GoGogot&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 Gogogot are strengthening or weakening over time.
Gogogot vs 代替品
In the agent category, Gogogot scores 52.1/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Gogogot vs pocketpaw — Trust Score: 66.2/100
- Gogogot vs agent-clip — Trust Score: 47.9/100
- Gogogot vs KrillClaw — Trust Score: 54.8/100
重要なポイント
- Gogogot has a measured Nerq Trust Score of 52.1/100 (D) — a composite of independent signals, not a suitability judgment.
- Among agent tools, Gogogot scores near the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — セキュリティ, メンテナンス, ドキュメント, コンプライアンス, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
よくある質問
Gogogotは安全ですか?
Gogogotの信頼スコアは?
Gogogotのより安全な代替は何ですか?
Gogogotの安全性スコアはどのくらいの頻度で更新されますか?
規制環境でGogogotを使用できますか?
関連項目
Disclaimer: Nerqの信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。