Czy Devici jest bezpieczny?

Devici — Nerq Trust Score 42.5/100 (Ocena E). Na podstawie analizy 3 wymiarów zaufania, jest ma istotne obawy dotyczące bezpieczeństwa. Ostatnia aktualizacja: 2026-04-22.

Zachowaj ostrożność z Devici. Devici to software tool z wynikiem zaufania Nerq 42.5/100 (E), based on 3 niezależnych wymiarów danych. Poniżej zweryfikowanego progu Nerq Konserwacja: 0/100. Popularność: 0/100. Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: 2026-04-22. Dane odczytywalne maszynowo (JSON).

Czy Devici jest bezpieczny?

NO — USE WITH CAUTION — Devici has a Nerq Trust Score of 42.5/100 (E). Ma poniżej przeciętne sygnały zaufania ze znaczącymi lukami in bezpieczeństwo, konserwacja, or dokumentacja. Not recommended for production use without thorough manual review and additional bezpieczeństwo measures.

Analiza bezpieczeństwa → Raport prywatności Devici →

Jaki jest wynik zaufania Devici?

Devici ma Nerq Trust Score 42.5/100 z oceną E. Ten wynik opiera się na 3 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.

Konserwacja
0
Dokumentacja
0
Popularność
0

Jakie są kluczowe ustalenia bezpieczeństwa dla Devici?

Najsilniejszy sygnał Devici to konserwacja na poziomie 0/100. Nie wykryto znanych luk w zabezpieczeniach. It has not yet reached the Nerq Verified threshold of 70+.

Konserwacja: 0/100 — niska aktywność konserwacji
Dokumentacja: 0/100 — ograniczona dokumentacja
Popularność: 0/100 — 4 gwiazdek na pulsemcp

Czym jest Devici i kto go utrzymuje?

Autorhttps://github.com/sdelements/devici-mcp
KategoriaBezpieczeństwo
Gwiazdki4
Źródłohttps://github.com/sdelements/devici-mcp

Popularne alternatywy w bezpieczeństwo

bee-san/Ciphey
69.9/100 · B-
github
usestrix/strix
69.6/100 · B-
github
SWE-agent/SWE-agent
68.8/100 · B-
github
promptfoo/promptfoo
66.2/100 · B-
github
TecharoHQ/anubis
72.3/100 · B
github

What Is Devici?

Devici is a bezpieczeństwo tool: Devici manages bezpieczeństwo 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 bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.

How Nerq Assesses Devici's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. 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 bezpieczeństwo, konserwacja, 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 — Sprawdź repository bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Devici's dependency tree.
  3. Opinia 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. Sprawdź 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 bezpieczeństwo 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. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency bezpieczeństwo

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

Update frequency

Regularly check for updates to Devici. Bezpieczeństwo 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 zgodność

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 zgodność with your bezpieczeństwo policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for bezpieczeństwo advisories

Subscribe to Devici's bezpieczeństwo 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 bezpieczeństwo 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 bezpieczeństwo 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 bezpieczeństwo tools. Organizations with strict bezpieczeństwo 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 umiarkowany 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 konserwacja 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 bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, 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 — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Devici are strengthening or weakening over time.

Devici vs Alternatywy

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

Kluczowe wnioski

Często zadawane pytania

Czy Devici jest bezpieczny?
Zachowaj ostrożność. Devici z wynikiem zaufania Nerq 42.5/100 (E). Najsilniejszy sygnał: konserwacja (0/100). Wynik oparty na Konserwacja (0/100), Popularność (0/100), Dokumentacja (0/100).
Jaki jest wynik zaufania Devici?
Devici: 42.5/100 (E). Wynik oparty na Konserwacja (0/100), Popularność (0/100), Dokumentacja (0/100). Oceny aktualizują się, gdy pojawiają się nowe dane. API: GET nerq.ai/v1/preflight?target=Devici
Jakie są bezpieczniejsze alternatywy dla Devici?
W kategorii Bezpieczeństwo, higher-rated alternatives include bee-san/Ciphey (70/100), usestrix/strix (70/100), SWE-agent/SWE-agent (69/100). Devici scores 42.5/100.
Jak często aktualizowana jest ocena bezpieczeństwa Devici?
Nerq continuously monitors Devici and updates its trust score as new data becomes available. Current: 42.5/100 (E), last zweryfikowane 2026-04-22. API: GET nerq.ai/v1/preflight?target=Devici
Czy mogę używać Devici w środowisku regulowanym?
Devici nie osiągnął progu weryfikacji Nerq 70. Zalecana dodatkowa weryfikacja.
API: /v1/preflight Trust Badge API Docs

Zobacz także

Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.

Używamy plików cookie do analiz i buforowania. Prywatność