Devici è sicuro?

Devici — Nerq Trust Score 42.5/100 (Grado E). Sulla base dell'analisi di 3 dimensioni di fiducia, è ha preoccupazioni di sicurezza notevoli. Ultimo aggiornamento: 2026-04-06.

Fai attenzione con Devici. Devici è un software tool con un Punteggio di fiducia Nerq di 42.5/100 (E), based on 3 dimensioni di dati indipendenti. Sotto la soglia verificata Nerq Manutenzione: 0/100. Popolarità: 0/100. Dati provenienti da molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Ultimo aggiornamento: 2026-04-06. Dati leggibili dalle macchine (JSON).

Devici è sicuro?

NO — USE WITH CAUTION — Devici has a Nerq Trust Score of 42.5/100 (E). Ha segnali di fiducia inferiori alla media con lacune significative in sicurezza, manutenzione, or documentazione. Not recommended for production use without thorough manual review and additional sicurezza measures.

Analisi di Sicurezza → Report sulla privacy di Devici →

Qual è il punteggio di fiducia di Devici?

Devici ha un Nerq Trust Score di 42.5/100 con voto E. Questo punteggio si basa su 3 dimensioni misurate indipendentemente, tra cui sicurezza, manutenzione e adozione della community.

Manutenzione
0
Documentazione
0
Popolarità
0

Quali sono i risultati di sicurezza chiave per Devici?

Il segnale più forte di Devici è manutenzione a 0/100. Non sono state rilevate vulnerabilità note. It has not yet reached the Nerq Verified threshold of 70+.

Manutenzione: 0/100 — bassa attività di manutenzione
Documentazione: 0/100 — documentazione limitata
Popolarità: 0/100 — 4 stelle su pulsemcp

Cos'è Devici e chi lo mantiene?

Autorehttps://github.com/sdelements/devici-mcp
CategoriaSicurezza
Stelle4
Fontehttps://github.com/sdelements/devici-mcp

Alternative popolari in sicurezza

bee-san/Ciphey
73.8/100 · B
github
usestrix/strix
73.8/100 · B
github
SWE-agent/SWE-agent
91.3/100 · A+
github
promptfoo/promptfoo
92.6/100 · A+
github
TecharoHQ/anubis
72.3/100 · B
github

What Is Devici?

Devici is a sicurezza tool: Devici manages sicurezza workflows in threat modeling.. It has 4 GitHub stars. Nerq Trust Score: 42/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sicurezza vulnerabilities, manutenzione activity, license conformità, and adozione della comunità.

How Nerq Assesses Devici's Safety

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

The overall Trust Score of 42.5/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 Devici?

Devici is designed for:

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

How to Verify Devici's Safety Yourself

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

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

Common Safety Concerns with Devici

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

Data handling

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

Dependency sicurezza

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

Update frequency

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

Third-party integrations

If Devici 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 conformità

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

Best Practices for Using Devici Safely

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

Conduct regular audits

Periodically review how Devici is used in your workflow. Check for unexpected behavior, permissions drift, and conformità with your sicurezza policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for sicurezza advisories

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

When Should You Avoid Devici?

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

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

How Devici Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among sicurezza tools, the average Trust Score is 67/100. Devici's score of 42.5/100 is below the category average of 67/100.

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

Devici vs Alternative

In the sicurezza category, Devici scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Punti chiave

Domande frequenti

Devici è sicuro?
Fai attenzione. Devici con un Punteggio di fiducia Nerq di 42.5/100 (E). Segnale più forte: manutenzione (0/100). Punteggio basato su Manutenzione (0/100), Popolarità (0/100), Documentazione (0/100).
Qual è il punteggio di fiducia di Devici?
Devici: 42.5/100 (E). Punteggio basato su Manutenzione (0/100), Popolarità (0/100), Documentazione (0/100). I punteggi si aggiornano quando nuovi dati diventano disponibili. API: GET nerq.ai/v1/preflight?target=Devici
What are safer alternatives to Devici?
Nella categoria Sicurezza, higher-rated alternatives include bee-san/Ciphey (74/100), usestrix/strix (74/100), SWE-agent/SWE-agent (91/100). Devici scores 42.5/100.
How often is Devici's safety score updated?
Nerq continuously monitors Devici and updates its trust score as new data becomes available. Dati provenienti da molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Current: 42.5/100 (E), last verificato 2026-04-06. API: GET nerq.ai/v1/preflight?target=Devici
Can I use Devici in a regulated environment?
Devici has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Vedi anche

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.

Utilizziamo i cookie per analisi e caching. Privacy