Är 96383 säker?

96383 — Nerq Förtroendepoäng 37.9/100 (Betyg E). Baserat på analys av 5 tillitsdimensioner bedöms det som har betydande säkerhetsrisker. Senast uppdaterad: 2026-04-02.

Var försiktig med 96383. 96383 is a software tool med ett Nerq-förtroendepoäng på 37.9/100 (E). Ligger under den rekommenderade gränsen på 70. Data hämtad från multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Senast uppdaterad: 2026-04-02. Maskinläsbar data (JSON).

Är 96383 säker?

NEJ — ANVÄND MED FÖRSIKTIGHET — 96383 har ett Nerq-förtroendepoäng på 37.9/100 (E). Har lägre än genomsnittliga förtroendesignaler med betydande luckor i säkerhet, underhåll eller dokumentation. Rekommenderas inte för produktionsanvändning utan noggrann manuell granskning och ytterligare säkerhetsåtgärder.

Säkerhetsanalys → {name} integritetsrapport →

Vad är 96383s förtroendepoäng?

96383 har ett Nerq-förtroendepoäng på 37.9/100, earning a E grade. This score is based on 5 independently measured dimensioner including säkerhet, underhåll, and communityanvändning.

Övergripande förtroende
37.9

Vilka är de viktigaste säkerhetsresultaten för 96383?

96383's strongest signal is övergripande förtroende at 37.9/100. No kända sårbarheter have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Sammansatt förtroendepoäng: 37.9/100 utifrån alla tillgängliga signaler

Vad är 96383 och vem underhåller det?

Utvecklare0xd0ebb635ab5d0a2403734e1f989195dbf8652517
Kategoriuncategorized
Källahttps://8004scan.io/agents/96383

What Is 96383?

96383 is a software tool in the uncategorized category: 8169407422645193487069208709206985488198237169032995008796847104492240. Nerq Förtroendepoäng: 38/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including säkerhet vulnerabilities, underhåll activity, license regelefterlevnad, and communityanvändning.

How Nerq Assesses 96383'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 dimensioner: Säkerhet (known CVEs, dependency vulnerabilities, säkerhet policies), Underhåll (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdiktions), and Community (stars, forks, downloads, ecosystem integrations).

96383 receives an overall Förtroendepoäng of 37.9/100 (E), which Nerq considers low. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

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

Each dimension is weighted according to its importance for the tool's category. For example, Säkerhet and Underhåll 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 96383's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimensioner, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).

Who Should Use 96383?

96383 is designed for:

Risk guidance: We recommend caution with 96383. The low trust score suggests potential risks in säkerhet, underhåll, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify 96383's Safety Yourself

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

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

Common Safety Concerns with 96383

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

Data handling

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

Dependency säkerhet

Check 96383's dependency tree for kända sårbarheter. Tools with outdated or unmaintained dependencies pose a higher säkerhet risk.

Update frequency

Regularly check for updates to 96383. Säkerhet patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If 96383 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 regelefterlevnad

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

Best Practices for Using 96383 Safely

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

Conduct regular audits

Periodically review how 96383 is used in your workflow. Check for unexpected behavior, permissions drift, and regelefterlevnad with your säkerhet policies.

Keep dependencies updated

Ensure 96383 and all its dependencies are running the latest stable versions to benefit from säkerhet patches.

Follow least privilege

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

Monitor for säkerhet advisories

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

When Should You Avoid 96383?

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

förtroendepoängen för

For each scenario, evaluate whether 96383 är 37.9/100 meets your organization's risk tolerance. We recommend running a manual säkerhet assessment alongside the automated Nerq score.

How 96383 Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Förtroendepoäng is 62/100. 96383's score of 37.9/100 is below the category average of 62/100.

This suggests that 96383 trails behind many comparable uncategorized tools. Organizations with strict säkerhet 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 måttlig 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.

Förtroendepoäng History

Nerq continuously monitors 96383 and recalculates its Förtroendepoäng 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 underhåll patterns change, 96383'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äkerhet and quality. Conversely, a downward trend may signal reduced underhåll, growing technical debt, or unresolved vulnerabilities. To track 96383's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=96383&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äkerhet, underhåll, dokumentation, regelefterlevnad, and community — has evolved independently, providing granular visibility into which aspects of 96383 are strengthening or weakening over time.

Viktigaste slutsatser

Vanliga frågor

Är 96383 säker att använda?
Var försiktig. 96383 har ett Nerq-förtroendepoäng på 37.9/100 (E). Starkaste signalen: övergripande förtroende (37.9/100). Poäng baserad på flera förtroendedimensioner.
Vad är 96383's trust score?
96383: 37.9/100 (E). Poäng baserad på: flera förtroendedimensioner. Poäng uppdateras när ny data finns tillgänglig. API: GET nerq.ai/v1/preflight?target=96383
Vilka säkrare alternativ finns till 96383?
In the uncategorized category, more software tools are being analyzed — kom tillbaka snart. 96383 scores 37.9/100.
How often is 96383's safety score updated?
Nerq continuously monitors 96383 and updates its trust score as new data becomes available. Data hämtad från multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 37.9/100 (E), last verifierad 2026-04-02. API: GET nerq.ai/v1/preflight?target=96383
Kan jag använda 96383 i en reglerad miljö?
96383 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: Nerqs förtroendepoäng är automatiserade bedömningar baserade på offentligt tillgängliga signaler. De utgör inte rekommendationer eller garantier. Gör alltid din egen verifiering.

We use cookies for analytics and caching. Integritet Policy