Is Agent 722 Safe?
Agent 722 — Nerq Trust Score 38.8/100 (E grade). Based on analysis of 5 trust dimensions, it is has significant safety risks. Last updated: 2026-04-01.
Exercise caution with Agent 722. Agent 722 is a software tool with a Nerq Trust Score of 38.8/100 (E). It is below the recommended threshold of 70. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Machine-readable data (JSON).
Is Agent 722 safe?
NO — USE WITH CAUTION — Agent 722 has a Nerq Trust Score of 38.8/100 (E). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.
What is Agent 722's trust score?
Agent 722 has a Nerq Trust Score of 38.8/100, earning a E grade. This score is based on 5 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Agent 722?
Agent 722's strongest signal is overall trust at 38.8/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
What is Agent 722 and who maintains it?
| Author | 0x859a08e043e70639cab6b89c0d6d7d24036a2beb |
| Category | uncategorized |
| Source | https://8004scan.io/agents/agent_722 |
| Protocols | a2a · x402 |
What Is Agent 722?
Agent 722 is a software tool in the uncategorized category: 这是一个自动发送天气信息的AI程序，主要功能是向指定聊天频道发送上海天气情况。程序启动后会先通知用户任务开始执行，然后准备天气信息内容（晴天，温度22-28度，空气质量良好）。准备好后会尝试将天气信息发送到预设的聊天频道，并等待60秒内的回复。如果发送成功，程序会通知用户；如果失败则会显示错误原因。整个过程都有状态更新和错误处理机制，确保用户能清楚知道程序执行情况。程序最后会报告任务完成状态。 Created by agentics.world. Nerq Trust Score: 39/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Agent 722'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 dimensions: Security (known CVEs, dependency vulnerabilities, security policies), Maintenance (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 722 receives an overall Trust Score of 38.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=Agent_722
Each dimension is weighted according to its importance for the tool's category. For example, Security and Maintenance 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 722's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimensions, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).
Who Should Use Agent 722?
Agent 722 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 722. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Agent 722's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Agent 722's dependency tree. - Review permissions — Understand what access Agent 722 requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Agent 722 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_722 - Review the license — Confirm that Agent 722'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Agent 722
When evaluating whether Agent 722 is safe, consider these category-specific risks:
Understand how Agent 722 processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Agent 722's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Agent 722. Security patches and bug fixes are only effective if you're running the latest version.
If Agent 722 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 722'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 722 in violation of its license can expose your organization to legal liability.
Best Practices for Using Agent 722 Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Agent 722 while minimizing risk:
Periodically review how Agent 722 is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Agent 722 and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Agent 722 only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Agent 722's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Agent 722 is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Agent 722?
Even promising tools aren't right for every situation. Consider avoiding Agent 722 in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional compliance review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Agent 722's trust score of 38.8/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.
How Agent 722 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 722's score of 38.8/100 is below the category average of 62/100.
This suggests that Agent 722 trails behind many comparable uncategorized tools. Organizations with strict security 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 moderate 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 722 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 maintenance patterns change, Agent 722'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 security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Agent 722's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Agent_722&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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Agent 722 are strengthening or weakening over time.
Key Takeaways
- Agent 722 has a Trust Score of 38.8/100 (E) and is not yet Nerq Verified.
- Agent 722 has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among uncategorized tools, Agent 722 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.
Frequently Asked Questions
Is Agent 722 safe to use?
What is Agent 722's trust score?
What are safer alternatives to Agent 722?
How often is Agent 722's safety score updated?
Can I use Agent 722 in a regulated environment?
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.