96201 Güvenli mi?

96201 — Nerq Trust Score 37.9/100 (E notu). 5 güven boyutunun analizine dayanarak, önemli güvenlik riskleri var olarak değerlendirilmektedir. Son güncelleme: 2026-04-01.

96201 konusunda dikkatli olun. 96201 is a software tool Nerq Güven Puanı ile 37.9/100 (E). Önerilen 70 eşiğinin altındadır. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Makine tarafından okunabilir veri (JSON).

96201 Güvenli mi?

HAYIR — DİKKATLİ KULLANIN — 96201 Nerq Güven Puanına sahip 37.9/100 (E). Güvenlik, bakım veya dokümantasyonda önemli boşluklarla birlikte ortalamanın altında güven sinyallerine sahiptir. Kapsamlı manuel inceleme ve ek güvenlik önlemleri olmadan üretim kullanımı için önerilmez.

Güvenlik Analizi → {name} Gizlilik Raporu →

96201'in güven puanı nedir?

96201'in Nerq Güven Puanı 37.9/100 olup E notu almıştır. Bu puan 5 bağımsız olarak ölçülen boyuta dayanmaktadır.

Genel Güven
37.9

96201 için temel güvenlik bulguları nelerdir?

96201'in en güçlü sinyali 37.9/100 ile genel güven'dir. Bilinen güvenlik açığı tespit edilmemiştir. Henüz Nerq Doğrulanmış eşiğine (70+) ulaşamamıştır.

Bileşik güven puanı: 37.9/100 tüm mevcut sinyaller genelinde

96201 nedir ve kim tarafından yönetilmektedir?

Geliştirici0x9532aa39ad0f94ef8c4690738ef584e4299e8fe0
Kategoriuncategorized
Kaynakhttps://8004scan.io/agents/96201

What Is 96201?

96201 is a software tool in the uncategorized category: 212408088996969599329753443352384494842300415715417955063191880. Nerq Trust Score: 38/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses 96201'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: Güvenlik (known CVEs, dependency vulnerabilities, security policies), Bakım (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).

96201 receives an overall Trust Score 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=96201

Each dimension is weighted according to its importance for the tool's category. For example, Security 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 96201'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 Should Use 96201?

96201 is designed for:

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

How to Verify 96201's Safety Yourself

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

  1. Check the source code — Review the repository security 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 96201's dependency tree.
  3. İnceleme permissions — Understand what access 96201 requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run 96201 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=96201
  6. İnceleyin license — Confirm that 96201'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with 96201

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

Data handling

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

Dependency security

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

Update frequency

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

Third-party integrations

If 96201 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 compliance

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

Best Practices for Using 96201 Safely

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

Conduct regular audits

Periodically review how 96201 is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid 96201?

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

For each scenario, evaluate whether 96201 güven puanı 37.9/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

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

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

Temel Çıkarımlar

Sık Sorulan Sorular

96201 kullanımı güvenli mi?
Dikkatli olun. 96201 Nerq Güven Puanına sahip 37.9/100 (E). En güçlü sinyal: genel güven (37.9/100). Puan şuna dayalı: birden fazla güven boyutu.
96201's trust score Nedir?
96201: 37.9/100 (E). Puan şuna dayalı:: birden fazla güven boyutu. Puanlar, yeni veriler kullanılabilir hale geldikçe güncellenir. API: GET nerq.ai/v1/preflight?target=96201
96201 için daha güvenli alternatifler nelerdir?
uncategorized kategorisinde, more software tools are being analyzed — yakında tekrar kontrol edin. 96201, 37.9/100 puan aldı.
How often is 96201's safety score updated?
Nerq continuously monitors 96201 and updates its trust score as new data becomes available. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 37.9/100 (E), last verified 2026-04-01. API: GET nerq.ai/v1/preflight?target=96201
96201 düzenlenmiş bir ortamda kullanabilir miyim?
96201 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: Nerq güven puanları, kamuya açık sinyallere dayanan otomatik değerlendirmelerdir. Tavsiye veya garanti niteliğinde değildir. Her zaman kendi doğrulamanızı yapın.

We use cookies for analytics and caching. Gizlilik Policy