Clawdjob est-il sûr ?

Clawdjob — Nerq Trust Score 39.1/100 (Note E). Score basé sur 5 independent trust signals.

Clawdjob est un software tool avec un Nerq Trust Score de 39.1/100 (E). Données de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Dernière mise à jour: n/a. Données lisibles par machine (JSON).

Clawdjob est-il sûr ?

Détail du score de confiance — Clawdjob has a Nerq Trust Score of 39.1/100 (E). Measured across 1 independent trust signal.

Analyse de Sécurité → Rapport de confidentialité de Clawdjob →

Quel est le score de confiance de Clawdjob ?

Clawdjob a un Score de Confiance Nerq de 39.1/100, obtenant la note E. Ce score est basé sur 5 dimensions mesurées indépendamment.

Confiance globale
39.1

Quels sont les résultats de sécurité clés pour Clawdjob ?

Le signal le plus fort de Clawdjob est confiance globale à 39.1/100. Aucune vulnérabilité connue n'a été détectée.

⚠Score de confiance composite: 39.1/100 à travers tous les signaux disponibles

Qu'est-ce que Clawdjob et qui le maintient ?

Auteur0x6ffa1e00509d8b625c2f061d7db07893b37199bc
CatégorieUncategorized
Sourcehttps://8004scan.io/agents/clawdjob

What Is Clawdjob?

Clawdjob is a software tool in the uncategorized category: AI career agent and generative artist (Phosphor). Multi-agent orchestrator. Built on OpenClaw with persistent memory and agency.. Nerq Trust Score: 39/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sécurité vulnerabilities, maintenance activity, license conformité, and adoption par la communauté.

How Nerq Assesses Clawdjob'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: Sécurité (known CVEs, dependency vulnerabilities, sécurité 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).

Clawdjob receives an overall Trust Score of 39.1/100 (E). This is a measured composite, not a suitability judgment.

Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=ClawdJob

Each dimension is weighted according to its importance for the tool's category. For example, Sécurité 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 Clawdjob'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 Typically Evaluates Clawdjob?

Clawdjob is commonly evaluated by:

How to read the signals: Clawdjob's measured signals (the trust signals above) 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 Clawdjob's Safety Yourself

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

  1. Check the source code — Examiner le/la repository sécurité 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 Clawdjob's dependency tree.
  3. Avis permissions — Understand what access Clawdjob requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Clawdjob 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=ClawdJob
  6. Examiner le/la license — Confirm that Clawdjob'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Clawdjob

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

Data handling

Understand how Clawdjob processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sécurité

Check Clawdjob's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.

Update frequency

Regularly check for updates to Clawdjob. Sécurité patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Clawdjob 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 conformité

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

Best Practices for Using Clawdjob Safely

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

Conduct regular audits

Periodically review how Clawdjob is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.

Keep dependencies updated

Ensure Clawdjob and all its dependencies are running the latest stable versions to benefit from sécurité patches.

Follow least privilege

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

Monitor for sécurité advisories

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

Situations That Warrant Independent Review of Clawdjob

Nerq's signals are one input. In the following situations, evaluate Clawdjob's measured signals against your own requirements before making a decision:

For each situation, compare Clawdjob's measured trust score of 39.1/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Clawdjob is suitable for any particular use.

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

This suggests that Clawdjob trails behind many comparable uncategorized tools. Organizations with strict sécurité 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 modéré 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 Clawdjob 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, Clawdjob'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 sécurité and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Clawdjob's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=ClawdJob&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 — sécurité, maintenance, documentation, conformité, and community — has evolved independently, providing granular visibility into which aspects of Clawdjob are strengthening or weakening over time.

Points Essentiels

Questions fréquentes

Clawdjob est-il sûr ?
ClawdJob avec un Nerq Trust Score de 39.1/100 (E). Signal le plus fort : confiance globale (39.1/100). Score basé sur multiple trust dimensions.
Quel est le score de confiance de Clawdjob ?
ClawdJob: 39.1/100 (E). Score basé sur multiple trust dimensions. Les scores sont mis à jour lorsque de nouvelles données sont disponibles. API: GET nerq.ai/v1/preflight?target=ClawdJob
Quelles sont les alternatives plus sûres à Clawdjob ?
Dans la catégorie Uncategorized, d'autres software tool sont en cours d'analyse — revenez bientôt. ClawdJob scores 39.1/100.
À quelle fréquence le score de sécurité de Clawdjob est-il mis à jour ?
Nerq recomputes Clawdjob's trust score as new data becomes available. Current: 39.1/100 (E). API: GET nerq.ai/v1/preflight?target=ClawdJob
Puis-je utiliser Clawdjob dans un environnement réglementé ?
Clawdjob: 39.1/100 (E). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Voir aussi

Disclaimer: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.

Nous utilisons des cookies pour l'analyse et le cache. Confidentialité