Er Runclawbot sikker?

Runclawbot — Nerq Trust Score 38.3/100 (Karakter E). Baseret på analyse af 3 tillidsdimensioner vurderes det som har betydelige sikkerhedsrisici. Sidst opdateret: 2026-04-22.

Vær forsigtig med Runclawbot. Runclawbot er en software tool med en Nerq Tillidsscore på 38.3/100 (E), based on 3 uafhængige datadimensioner. Under Nerqs verificerede tærskel Vedligeholdelse: 0/100. Popularitet: 0/100. Data hentet fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sidst opdateret: 2026-04-22. Maskinlæsbare data (JSON).

Er Runclawbot sikker?

NO — USE WITH CAUTION — Runclawbot has a Nerq Trust Score of 38.3/100 (E). Har under gennemsnitlige tillidssignaler med betydelige huller in sikkerhed, vedligeholdelse, or dokumentation. Not recommended for production use without thorough manual review and additional sikkerhed measures.

Sikkerhedsanalyse → Runclawbot privatlivsrapport →

Hvad er Runclawbots tillidsscore?

Runclawbot har en Nerq Trust Score på 38.3/100 med karakteren E. Denne score er baseret på 3 uafhængigt målte dimensioner, herunder sikkerhed, vedligeholdelse og community-adoption.

Vedligeholdelse
0
Dokumentation
0
Popularitet
0

Hvad er de vigtigste sikkerhedsresultater for Runclawbot?

Runclawbots stærkeste signal er vedligeholdelse på 0/100. Ingen kendte sårbarheder er fundet. It has not yet reached the Nerq Verified threshold of 70+.

Vedligeholdelse: 0/100 — lav vedligeholdelsesaktivitet
Dokumentation: 0/100 — begrænset dokumentation
Popularitet: 0/100 — community-adoption

Hvad er Runclawbot og hvem vedligeholder det?

Udvikler0xaeb39bccc3c6ffd0307b27a277913b7becbd414c
KategoriMarketing
Kildehttps://8004scan.io/agents/runclawbot

Populære alternativer i marketing

sansan0/TrendRadar
68.2/100 · B-
github
srbhr/Resume-Matcher
66.2/100 · B-
github
friuns2/BlackFriday-GPTs-Prompts
66.8/100 · B-
github
coreyhaines31/marketingskills
73.4/100 · B
github
RayVentura/ShortGPT
72.8/100 · B
github

What Is Runclawbot?

Runclawbot is a software tool in the marketing category: Autonomous trend tokenization agent for culture amplification and deployment.. Nerq Trust Score: 38/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhed vulnerabilities, vedligeholdelse activity, license overholdelse, and fællesskabsadoption.

How Nerq Assesses Runclawbot's Safety

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

The overall Trust Score of 38.3/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 Runclawbot?

Runclawbot is designed for:

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

How to Verify Runclawbot's Safety Yourself

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

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

Common Safety Concerns with Runclawbot

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

Data handling

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

Dependency sikkerhed

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

Update frequency

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

Third-party integrations

If Runclawbot 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 overholdelse

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

Best Practices for Using Runclawbot Safely

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

Conduct regular audits

Periodically review how Runclawbot is used in your workflow. Check for unexpected behavior, permissions drift, and overholdelse with your sikkerhed policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for sikkerhed advisories

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

When Should You Avoid Runclawbot?

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

For each scenario, evaluate whether Runclawbot's trust score of 38.3/100 meets your organization's risk tolerance. We recommend running a manual sikkerhed assessment alongside the automated Nerq score.

How Runclawbot Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among marketing tools, the average Trust Score is 62/100. Runclawbot's score of 38.3/100 is below the category average of 62/100.

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

Runclawbot vs Alternativer

In the marketing category, Runclawbot scores 38.3/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Vigtigste pointer

Ofte stillede spørgsmål

Er Runclawbot sikker?
Vær forsigtig. RUNCLAWBOT med en Nerq Tillidsscore på 38.3/100 (E). Stærkeste signal: vedligeholdelse (0/100). Score baseret på Vedligeholdelse (0/100), Popularitet (0/100), Dokumentation (0/100).
Hvad er Runclawbots tillidsscore?
RUNCLAWBOT: 38.3/100 (E). Score baseret på Vedligeholdelse (0/100), Popularitet (0/100), Dokumentation (0/100). Scorer opdateres når nye data bliver tilgængelige. API: GET nerq.ai/v1/preflight?target=RUNCLAWBOT
Hvad er sikrere alternativer til Runclawbot?
I kategorien Marketing, higher-rated alternatives include sansan0/TrendRadar (68/100), srbhr/Resume-Matcher (66/100), friuns2/BlackFriday-GPTs-Prompts (67/100). RUNCLAWBOT scores 38.3/100.
Hvor ofte opdateres Runclawbots sikkerhedsscore?
Nerq continuously monitors Runclawbot and updates its trust score as new data becomes available. Current: 38.3/100 (E), last verificeret 2026-04-22. API: GET nerq.ai/v1/preflight?target=RUNCLAWBOT
Kan jeg bruge Runclawbot i et reguleret miljø?
Runclawbot har ikke nået Nerq-verificeringstærsklen på 70. Yderligere gennemgang anbefales.
API: /v1/preflight Trust Badge API Docs

Se også

Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.

Vi bruger cookies til analyse og caching. Privatliv