Ist Clawcoded sicher?

Clawcoded — Nerq Trust Score 42.4/100 (Note E). Basierend auf der Analyse von 3 Vertrauensdimensionen wird es als bemerkenswerte Sicherheitsbedenken eingestuft. Zuletzt aktualisiert: 2026-03-31.

Vorsicht bei Clawcoded. Clawcoded is a software tool mit einer Nerq-Vertrauensbewertung von 42.4/100 (E), based on 3 independent data dimensions. It is below the recommended threshold of 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Maschinenlesbare Daten (JSON).

Ist Clawcoded sicher?

NO — USE WITH CAUTION — Clawcoded hat eine Nerq-Vertrauensbewertung von 42.4/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.

Sicherheitsanalyse → {name} Datenschutzbericht →

Was ist die Vertrauensbewertung von Clawcoded?

Clawcoded hat eine Nerq-Vertrauensbewertung von 42.4/100 und erhält die Note E. Diese Bewertung basiert auf 3 unabhängig gemessenen Dimensionen.

Wartung
0
Dokumentation
0
Beliebtheit
0

Was sind die wichtigsten Sicherheitsergebnisse für Clawcoded?

Das stärkste Signal von Clawcoded ist wartung mit 0/100. Es wurden keine bekannten Schwachstellen erkannt. Hat die Nerq-Vertrauensschwelle von 70+ noch nicht erreicht.

Maintenance: 0/100 — low maintenance activity
Documentation: 0/100 — limited documentation
Popularity: 0/100 — 1 stars on erc8004

Was ist Clawcoded und wer pflegt es?

Autor0x00bd00749ea0cbb28c6e9c4ef0d95263aabcc0fd
Kategorieinfrastructure
Sterne1
Quellehttps://8004scan.io/agents/clawcoded
Protocolsx402

Beliebte Alternativen in infrastructure

n8n-io/n8n
78.5/100 · B
github
langflow-ai/langflow
87.6/100 · A
github
langgenius/dify
79.1/100 · B
github
open-webui/open-webui
74.8/100 · B
github
google-gemini/gemini-cli
71.8/100 · B
github

What Is Clawcoded?

Clawcoded is a software tool in the infrastructure category: Multi-purpose AI agent platform running on OpenClaw. Handles coding, DeFi trading, automation, and system operations. MCP server with tools, prompts, and resources available.. It has 1 GitHub stars. Nerq Trust Score: 42/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 Clawcoded's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Clawcoded performs in each:

The overall Trust Score of 42.4/100 (E) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Who Should Use Clawcoded?

Clawcoded is designed for:

Risk guidance: We recommend caution with Clawcoded. 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 Clawcoded's Safety Yourself

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

  1. Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Clawcoded's dependency tree.
  3. Bewertung permissions — Understand what access Clawcoded requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Clawcoded 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=ClawCoded
  6. Überprüfen Sie das/die license — Confirm that Clawcoded'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Clawcoded

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

Data handling

Understand how Clawcoded processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Clawcoded's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Clawcoded. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Clawcoded 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 compliance

Verify that Clawcoded's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Clawcoded in violation of its license can expose your organization to legal liability.

Best Practices for Using Clawcoded Safely

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

Conduct regular audits

Periodically review how Clawcoded is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Clawcoded and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

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

Monitor for security advisories

Subscribe to Clawcoded's security 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 Clawcoded is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Clawcoded?

Even promising tools aren't right for every situation. Consider avoiding Clawcoded in these scenarios:

Die Vertrauensbewertung von

For each scenario, evaluate whether Clawcoded von 42.4/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Clawcoded 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. Clawcoded's score of 42.4/100 is below the category average of 62/100.

This suggests that Clawcoded trails behind many comparable infrastructure 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 Clawcoded 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, Clawcoded'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 Clawcoded's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=ClawCoded&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 Clawcoded are strengthening or weakening over time.

Clawcoded vs Alternatives

In the infrastructure category, Clawcoded erzielt 42.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Wichtigste Punkte

Häufig gestellte Fragen

Ist Clawcoded sicher in der Verwendung?
Vorsicht walten lassen. ClawCoded hat eine Nerq-Vertrauensbewertung von 42.4/100 (E). Stärkstes Signal: wartung (0/100). Score based on maintenance (0/100), popularity (0/100), documentation (0/100).
Was ist Clawcoded's trust score?
ClawCoded: 42.4/100 (E). Score based on: maintenance (0/100), popularity (0/100), documentation (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=ClawCoded
Was sind sicherere Alternativen zu Clawcoded?
In the infrastructure category, higher-rated alternatives include n8n-io/n8n (78/100), langflow-ai/langflow (88/100), langgenius/dify (79/100). ClawCoded erzielt 42.4/100.
How often is Clawcoded's safety score updated?
Nerq continuously monitors Clawcoded and updates its trust score as new data becomes available. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 42.4/100 (E), last verified 2026-03-31. API: GET nerq.ai/v1/preflight?target=ClawCoded
Can I use Clawcoded in a regulated environment?
Clawcoded has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq-Vertrauensbewertungen sind automatisierte Bewertungen basierend auf öffentlich verfügbaren Signalen. Sie sind keine Empfehlungen oder Garantien. Führen Sie immer Ihre eigene Sorgfaltsprüfung durch.

We use cookies for analytics and caching. Datenschutz Policy