Безопасен ли Agent 17367?
Agent 17367 — Nerq Trust Score 39.1/100 (Оценка E). На основе анализа 5 измерений доверия, считается имеющим значительные риски безопасности. Последнее обновление: 2026-04-23.
Будьте осторожны с Agent 17367. Agent 17367 — это software tool с рейтингом доверия Nerq 39.1/100 (E). Ниже верифицированного порога Nerq Данные из множественные публичные источники, включая реестры пакетов, GitHub, NVD, OSV.dev и OpenSSF Scorecard. Последнее обновление: 2026-04-23. Машинночитаемые данные (JSON).
Безопасен ли Agent 17367?
NO — USE WITH CAUTION — Agent 17367 has a Nerq Trust Score of 39.1/100 (E). Сигналы доверия ниже среднего со значительными пробелами in безопасность, обслуживание, or документация. Not recommended for production use without thorough manual review and additional безопасность measures.
Каков рейтинг доверия Agent 17367?
Agent 17367 имеет Nerq Trust Score 39.1/100 с оценкой E. Этот балл основан на 5 независимо измеренных параметрах, включая безопасность, обслуживание и принятие сообществом.
Каковы основные выводы по безопасности Agent 17367?
Самый сильный сигнал Agent 17367 — общее доверие на уровне 39.1/100. Известных уязвимостей не обнаружено. It has not yet reached the Nerq Verified threshold of 70+.
Что такое Agent 17367 и кто его поддерживает?
| Разработчик | 0x5d080b5d2718bd65678c9582519eb876c3042511 |
| Категория | Uncategorized |
| Источник | https://8004scan.io/agents/agent-17367 |
| Protocols | x402 |
What Is Agent 17367?
Agent 17367 is a software tool in the uncategorized category: Personal AI assistant - direct, warm, energetic. Built on OpenClaw.. Nerq Trust Score: 39/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including безопасность vulnerabilities, обслуживание activity, license соответствие, and принятие сообществом.
How Nerq Assesses Agent 17367'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 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).
Agent 17367 receives an overall Trust Score of 39.1/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=Agent 17367
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 Agent 17367'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 Agent 17367?
Agent 17367 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 Agent 17367. 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 Agent 17367'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 known vulnerabilities in Agent 17367's dependency tree. - Отзыв permissions — Understand what access Agent 17367 requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Agent 17367 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=Agent 17367 - Проверьте license — Confirm that Agent 17367'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 Agent 17367
When evaluating whether Agent 17367 is safe, consider these category-specific risks:
Understand how Agent 17367 processes, stores, and transmits your data. Проверьте tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Agent 17367's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher безопасность risk.
Regularly check for updates to Agent 17367. Безопасность patches and bug fixes are only effective if you're running the latest version.
If Agent 17367 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 Agent 17367's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Agent 17367 in violation of its license can expose your organization to legal liability.
Best Practices for Using Agent 17367 Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Agent 17367 while minimizing risk:
Periodically review how Agent 17367 is used in your workflow. Check for unexpected behavior, permissions drift, and соответствие with your безопасность policies.
Ensure Agent 17367 and all its dependencies are running the latest stable versions to benefit from безопасность patches.
Grant Agent 17367 only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Agent 17367's безопасность advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Agent 17367 is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Agent 17367?
Even promising tools aren't right for every situation. Consider avoiding Agent 17367 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 Agent 17367's trust score of 39.1/100 meets your organization's risk tolerance. We recommend running a manual безопасность assessment alongside the automated Nerq score.
How Agent 17367 Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Agent 17367's score of 39.1/100 is below the category average of 62/100.
This suggests that Agent 17367 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.
Trust Score History
Nerq continuously monitors Agent 17367 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, Agent 17367'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 Agent 17367's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Agent 17367&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 Agent 17367 are strengthening or weakening over time.
Основные выводы
- Agent 17367 has a Trust Score of 39.1/100 (E) and is not yet Nerq Verified.
- Agent 17367 has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among uncategorized tools, Agent 17367 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.
Какие данные собирает Agent 17367?
Конфиденциальность assessment for Agent 17367 is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.
Безопасен ли Agent 17367?
Безопасность score: на стадии оценки. Review безопасность practices and consider alternatives with higher безопасность scores for sensitive use cases.
Nerq отслеживает эту сущность по базам NVD, OSV.dev и реестровым базам уязвимостей для непрерывной оценки безопасности.
Полный анализ: Отчёт о безопасности Agent 17367
Как мы рассчитали этот рейтинг
Agent 17367's trust score of 39.1/100 (E) вычисляется из множественные публичные источники, включая реестры пакетов, GitHub, NVD, OSV.dev и OpenSSF Scorecard. Рейтинг отражает 0 независимых показателей: . Каждый показатель имеет равный вес в сводном рейтинге доверия.
Nerq анализирует более 7,5 миллиона сущностей в 26 реестрах используя единую методологию, что позволяет проводить прямое сравнение между сущностями. Рейтинги обновляются непрерывно по мере поступления новых данных.
Эта страница последний раз проверена: April 23, 2026. Версия данных: 1.0.
Полная документация методологии · Машинночитаемые данные (JSON API)
Часто задаваемые вопросы
Безопасен ли Agent 17367?
Каков рейтинг доверия Agent 17367?
Какие более безопасные альтернативы Agent 17367?
Как часто обновляется оценка безопасности Agent 17367?
Могу ли я использовать Agent 17367 в регулируемой среде?
См. также
Disclaimer: Рейтинги доверия Nerq — это автоматические оценки, основанные на публично доступных сигналах. Они не являются рекомендацией или гарантией. Всегда проводите собственную проверку.