هل 05914 آمن؟

05914 — Nerq Trust Score 37.9/100 (الدرجة E). بناءً على تحليل 5 أبعاد للثقة، يُعتبر لديه مخاطر أمنية كبيرة. آخر تحديث: 2026-04-02.

توخَّ الحذر مع 05914. 05914 is a software tool with a Nerq Trust Score of 37.9/100 (E). It is below the recommended threshold of 70. البيانات مصدرها قراءة آلية.

هل 05914 آمن؟

NO — USE WITH CAUTION — 05914 has a Nerq Trust Score of 37.9/100 (E). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

تحليل الأمان → تقرير الخصوصية →

ما هي درجة ثقة 05914؟

حصل 05914 على درجة ثقة Nerq تبلغ 37.9/100 بدرجة E. يعتمد هذا التقييم على 5 أبعاد مُقاسة بشكل مستقل.

الثقة الشاملة
37.9

ما هي النتائج الأمنية الرئيسية لـ 05914؟

أقوى إشارة لـ 05914 هي الثقة الشاملة بدرجة 37.9/100. لم يتم اكتشاف أي ثغرات أمنية معروفة. لم يصل بعد إلى عتبة التحقق من Nerq البالغة 70+.

Composite trust score: 37.9/100 across all available signals

ما هو 05914 ومن يديره؟

المؤلف0xb9dd2b1b1ec0b6b871d867623b198faf99ee6438
الفئةuncategorized
المصدرhttps://8004scan.io/agents/05914

What Is 05914?

05914 is a software tool in the uncategorized category: 1792604437773862296001445721258115846698164822434493525. 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 05914'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: Security (known CVEs, dependency vulnerabilities, security 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).

05914 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=05914

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 05914'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 05914?

05914 is designed for:

Risk guidance: We recommend caution with 05914. 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 05914'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 05914's dependency tree.
  3. Review permissions — Understand what access 05914 requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run 05914 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=05914
  6. Review the license — Confirm that 05914'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 05914

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

Data handling

Understand how 05914 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 05914's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

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

Third-party integrations

If 05914 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 05914's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using 05914 in violation of its license can expose your organization to legal liability.

Best Practices for Using 05914 Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid 05914?

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

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

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

This suggests that 05914 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.

درجة الثقة History

Nerq continuously monitors 05914 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, 05914'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 05914's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=05914&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 05914 are strengthening or weakening over time.

Key Takeaways

الأسئلة الشائعة

Is 05914 safe to use?
Exercise caution. 05914 has a Nerq Trust Score of 37.9/100 (E). Strongest signal: الثقة الشاملة (37.9/100). Score based on multiple trust dimensions.
ما هو 05914's trust score?
05914: 37.9/100 (E). Score based on: multiple trust dimensions. Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=05914
What are safer alternatives to 05914?
In the uncategorized category, more software tools are being analyzed — check back soon. 05914 scores 37.9/100.
How often is 05914's safety score updated?
Nerq continuously monitors 05914 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-02. API: GET nerq.ai/v1/preflight?target=05914
Can I use 05914 in a regulated environment?
05914 has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge واجهة برمجة التطبيقات Docs

Disclaimer: درجات ثقة Nerq هي تقييمات آلية مبنية على إشارات متاحة للعموم. وهي ليست توصيات أو ضمانات. قم دائمًا بإجراء العناية الواجبة الخاصة بك.

We use cookies for analytics and caching. الخصوصية Policy