Ist Clawpayer sicher?
Clawpayer — Nerq Trust Score 57.1/100 (Note D). Basierend auf der Analyse von 5 Vertrauensdimensionen wird es als bemerkenswerte Sicherheitsbedenken eingestuft. Zuletzt aktualisiert: 2026-04-03.
Verwende Clawpayer mit Vorsicht. Clawpayer ist ein software tool mit einem Nerq-Vertrauenswert von 57.1/100 (D), basierend auf 5 unabhängigen Datendimensionen. It is below the recommended threshold of 70. Sicherheit: 0/100. Wartung: 0/100. Beliebtheit: 0/100. Daten von multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Zuletzt aktualisiert: 2026-04-03. Maschinenlesbare Daten (JSON).
Ist Clawpayer sicher?
CAUTION — Clawpayer hat eine Nerq-Vertrauensbewertung von 57.1/100 (D). Es hat moderat Vertrauenssignale, zeigt aber einige Problembereiche that warrant attention. Suitable for development use — review Sicherheit and Wartung signals before production deployment.
Was ist die Vertrauensbewertung von Clawpayer?
Clawpayer hat eine Nerq-Vertrauensbewertung von 57.1/100 und erhält die Note D. Diese Bewertung basiert auf 5 unabhängig gemessenen Dimensionen.
Was sind die wichtigsten Sicherheitsergebnisse für Clawpayer?
Das stärkste Signal von Clawpayer ist konformität mit 82/100. Es wurden keine bekannten Schwachstellen erkannt. Hat die Nerq-Vertrauensschwelle von 70+ noch nicht erreicht.
Was ist Clawpayer und wer pflegt es?
| Autor | valdo99 |
| Kategorie | infrastructure |
| Quelle | https://github.com/valdo99/clawpayer |
| Protocols | mcp |
Regulatorische Konformität
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 82/100 |
| Gerichtsbarkeits | Assessed across 52 jurisdictions |
Beliebte Alternativen in infrastructure
What Is Clawpayer?
Clawpayer is a software tool in the infrastructure category: Secure card vault with policy-gated payments for AI agents. MCP server + OpenClaw plugin.. Nerq Trust Score: 57/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.
How Nerq Assesses Clawpayer's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five Dimensionen. Here is how Clawpayer performs in each:
- Sicherheit (0/100): Clawpayer's Sicherheit posture is poor. This score factors in known CVEs, dependency vulnerabilities, Sicherheit policy presence, and code signing practices.
- Wartung (0/100): Clawpayer is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API Dokumentation, usage examples, and contribution guidelines.
- Compliance (82/100): Clawpayer is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Basierend auf GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 57.1/100 (D) 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 Clawpayer?
Clawpayer is designed for:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Clawpayer is suitable for development and testing environments. Before production deployment, conduct a thorough review of its Sicherheit posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Clawpayer's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Überprüfen Sie das/die repository Sicherheit policy, open issues, and recent commits for signs of active Wartung.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Clawpayer's dependency tree. - Bewertung permissions — Understand what access Clawpayer requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Clawpayer 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=clawpayer - Überprüfen Sie das/die license — Confirm that Clawpayer'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 Sicherheit concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Clawpayer
When evaluating whether Clawpayer is safe, consider these category-specific risks:
Understand how Clawpayer processes, stores, and transmits your data. Überprüfen Sie das/die tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Clawpayer's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher Sicherheit risk.
Regularly check for updates to Clawpayer. Sicherheit patches and bug fixes are only effective if you're running the latest version.
If Clawpayer 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 Clawpayer's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Clawpayer in violation of its license can expose your organization to legal liability.
Clawpayer and the EU AI Act
Clawpayer is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.
Nerq's Konformität assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal Konformität.
Best Practices for Using Clawpayer Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Clawpayer while minimizing risk:
Periodically review how Clawpayer is used in your workflow. Check for unexpected behavior, permissions drift, and Konformität with your Sicherheit policies.
Ensure Clawpayer and all its dependencies are running the latest stable versions to benefit from Sicherheit patches.
Grant Clawpayer only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Clawpayer's Sicherheit advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Clawpayer is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Clawpayer?
Even promising tools aren't right for every situation. Consider avoiding Clawpayer in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional Konformität review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Clawpayer von 57.1/100 meets your organization's risk tolerance. We recommend running a manual Sicherheit assessment alongside the automated Nerq score.
How Clawpayer Vergleichens 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. Clawpayer's score of 57.1/100 is near the category average of 62/100.
This places Clawpayer in line with the typical infrastructure 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 moderat 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 Clawpayer 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 Wartung patterns change, Clawpayer'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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, growing technical debt, or unresolved vulnerabilities. To track Clawpayer's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=clawpayer&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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Clawpayer are strengthening or weakening over time.
Clawpayer vs Alternativen
In the infrastructure category, Clawpayer erzielt 57.1/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Clawpayer vs n8n — Trust Score: 78.5/100
- Clawpayer vs langflow — Trust Score: 87.6/100
- Clawpayer vs dify — Trust Score: 79.1/100
Wichtigste Punkte
- Clawpayer hat eine Vertrauensbewertung von 57.1/100 (D) and is not yet Nerq Verified.
- Clawpayer shows moderat trust signals. Conduct thorough due diligence before deploying to production environments.
- Among infrastructure tools, Clawpayer erzielt near 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.
Häufig gestellte Fragen
Ist Clawpayer sicher in der Verwendung?
Was ist Clawpayer's trust score?
Was sind sicherere Alternativen zu Clawpayer?
How often is Clawpayer's safety score updated?
Can I use Clawpayer in a regulated environment?
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.