Apakah Clawchess Aman?

Clawchess — Nerq Trust Score 49.8/100 (Nilai D). Berdasarkan analisis 1 dimensi kepercayaan, dianggap memiliki masalah keamanan yang perlu diperhatikan. Terakhir diperbarui: 2026-04-03.

Berhati-hatilah dengan Clawchess. Clawchess is a software tool dengan Skor Kepercayaan Nerq sebesar 49.8/100 (D), based on 3 dimensi data independen. Di bawah ambang batas yang direkomendasikan yaitu 70. Data bersumber dari multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Terakhir diperbarui: 2026-04-03. Data yang dapat dibaca mesin (JSON).

Apakah Clawchess Aman?

TIDAK — GUNAKAN DENGAN HATI-HATI — Clawchess memiliki Skor Kepercayaan Nerq sebesar 49.8/100 (D). Memiliki sinyal kepercayaan di bawah rata-rata dengan celah signifikan di keamanan, pemeliharaan, atau dokumentasi. Tidak direkomendasikan untuk penggunaan produksi tanpa tinjauan manual menyeluruh dan langkah keamanan tambahan.

Analisis Keamanan → Laporan Privasi {name} →

Berapa skor kepercayaan Clawchess?

Clawchess memiliki Skor Kepercayaan Nerq 49.8/100 dengan nilai D. Skor ini didasarkan pada 1 dimensi yang diukur secara independen.

Kepatuhan
96

Apa temuan keamanan utama untuk Clawchess?

Sinyal terkuat Clawchess adalah kepatuhan pada 96/100. Tidak ada kerentanan yang diketahui terdeteksi. Belum mencapai ambang verifikasi Nerq 70+.

Compliance: 96/100 — covers 49 of 52 jurisdictions

Apa itu Clawchess dan siapa yang mengelolanya?

Pembuateightangels
Kategoriuncategorized
Sumberhttps://huggingface.co/spaces/eightangels/clawchess
Protocolshuggingface_hub

Kepatuhan Regulasi

EU AI Act Risk ClassNot assessed
Compliance Score96/100
JurisdictionsAssessed across 52 jurisdictions

What Is Clawchess?

Clawchess is a software tool in the uncategorized category available on huggingface_space_full. Nerq Trust Score: 50/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including keamanan vulnerabilities, pemeliharaan activity, license kepatuhan, and adopsi komunitas.

How Nerq Assesses Clawchess's Safety

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

The overall Trust Score of 49.8/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 Clawchess?

Clawchess is designed for:

Risk guidance: We recommend caution with Clawchess. The low trust score suggests potential risks in keamanan, pemeliharaan, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Clawchess's Safety Yourself

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

  1. Check the source code — Tinjau repository keamanan policy, open issues, and recent commits for signs of active pemeliharaan.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Clawchess's dependency tree.
  3. Ulasan permissions — Understand what access Clawchess requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Clawchess 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=clawchess
  6. Tinjau license — Confirm that Clawchess'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 keamanan concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Clawchess

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

Data handling

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

Dependency keamanan

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

Update frequency

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

Third-party integrations

If Clawchess 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 kepatuhan

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

Best Practices for Using Clawchess Safely

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

Conduct regular audits

Periodically review how Clawchess is used in your workflow. Check for unexpected behavior, permissions drift, and kepatuhan with your keamanan policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for keamanan advisories

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

When Should You Avoid Clawchess?

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

Skor kepercayaan

For each scenario, evaluate whether Clawchess sebesar 49.8/100 meets your organization's risk tolerance. We recommend running a manual keamanan assessment alongside the automated Nerq score.

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

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

Kesimpulan Utama

Pertanyaan yang Sering Diajukan

Apakah Clawchess aman digunakan?
Berhati-hatilah. clawchess memiliki Skor Kepercayaan Nerq sebesar 49.8/100 (D). Sinyal terkuat: kepatuhan (96/100). Skor berdasarkan beberapa dimensi kepercayaan.
Berapa skor kepercayaan Clawchess?
clawchess: 49.8/100 (D). Skor berdasarkan: beberapa dimensi kepercayaan. Compliance: 96/100. Skor diperbarui saat data baru tersedia. API: GET nerq.ai/v1/preflight?target=clawchess
Apa alternatif yang lebih aman dari Clawchess?
Dalam kategori uncategorized, more software tools are being analyzed — kunjungi kembali segera. clawchess mendapat skor 49.8/100.
How often is Clawchess's safety score updated?
Nerq continuously monitors Clawchess and updates its trust score as new data becomes available. Data bersumber dari multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 49.8/100 (D), last terverifikasi 2026-04-03. API: GET nerq.ai/v1/preflight?target=clawchess
Bisakah saya menggunakan Clawchess di lingkungan teregulasi?
Clawchess 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: Skor kepercayaan Nerq adalah penilaian otomatis berdasarkan sinyal yang tersedia secara publik. Ini bukan rekomendasi atau jaminan. Selalu lakukan verifikasi mandiri Anda sendiri.

We use cookies for analytics and caching. Privasi Policy