Denue è sicuro?

Denue — Nerq Punteggio di fiducia 38.9/100 (Grado E). Sulla base dell'analisi di 5 dimensioni di fiducia, è ha rischi di sicurezza significativi. Ultimo aggiornamento: 2026-04-02.

Fai attenzione con Denue. Denue is a software tool con un Punteggio di fiducia Nerq di 38.9/100 (E). È al di sotto della soglia raccomandata di 70. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-02. Dati leggibili dalle macchine (JSON).

Denue è sicuro?

NO — USA CON CAUTELA — Denue ha un Punteggio di fiducia Nerq di 38.9/100 (E). Ha segnali di fiducia inferiori alla media con lacune significative in sicurezza, manutenzione o documentazione. Non raccomandato per uso in produzione senza una revisione manuale accurata e misure di sicurezza aggiuntive.

Analisi di Sicurezza → Report sulla privacy di {name} →

Qual è il punteggio di fiducia di Denue?

Denue ha un Punteggio di fiducia Nerq di 38.9/100, earning a E grade. This score is based on 5 independently measured dimensions including security, maintenance, and community adoption.

Fiducia complessiva
38.9

Quali sono i risultati di sicurezza chiave per Denue?

Denue's strongest signal is fiducia complessiva at 38.9/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Punteggio di fiducia complessivo: 38.9/100 su tutti i segnali disponibili

Cos'è Denue e chi lo mantiene?

Autorehttps://github.com/fectda/mcp-debue
Categoriauncategorized
Fontehttps://github.com/fectda/mcp-debue

What Is Denue?

Denue is a software tool in the uncategorized category: Provides access to INEGI's DENUE API for searching and counting commercial establishments in Mexico.. Nerq Punteggio di fiducia: 39/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 Denue'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: Sicurezza (known CVEs, dependency vulnerabilities, security policies), Manutenzione (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).

Denue receives an overall Punteggio di fiducia of 38.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=DENUE

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

Denue is designed for:

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

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

Data handling

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

Update frequency

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

Third-party integrations

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

Best Practices for Using Denue Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Denue?

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

punteggio di fiducia di

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

How Denue Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Punteggio di fiducia is 62/100. Denue's score of 38.9/100 is below the category average of 62/100.

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

Punteggio di fiducia History

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

Punti chiave

Domande frequenti

Denue è sicuro da usare?
Fai attenzione. DENUE ha un Punteggio di fiducia Nerq di 38.9/100 (E). Segnale più forte: fiducia complessiva (38.9/100). Punteggio basato su più dimensioni di fiducia.
Cos'è Denue's trust score?
DENUE: 38.9/100 (E). Punteggio basato su: più dimensioni di fiducia. I punteggi vengono aggiornati quando sono disponibili nuovi dati. API: GET nerq.ai/v1/preflight?target=DENUE
Quali sono le alternative più sicure a Denue?
Nella categoria uncategorized, more software tools are being analyzed — torna a controllare presto. DENUE ottiene 38.9/100.
How often is Denue's safety score updated?
Nerq continuously monitors Denue 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: 38.9/100 (E), last verified 2026-04-02. API: GET nerq.ai/v1/preflight?target=DENUE
Posso usare Denue in un ambiente regolamentato?
Denue 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: I punteggi di fiducia Nerq sono valutazioni automatizzate basate su segnali disponibili pubblicamente. Non costituiscono raccomandazioni o garanzie. Effettua sempre la tua verifica personale.

We use cookies for analytics and caching. Privacy Policy