Je Devici bezpečný?
Devici — Nerq Trust Score 42.5/100 (Stupeň E). Na základě analýzy 3 dimenzí důvěryhodnosti je má pozoruhodné bezpečnostní obavy. Naposledy aktualizováno: 2026-03-31.
Buďte opatrní s Devici. Devici is a software tool se skóre důvěryhodnosti Nerq 42.5/100 (E), based on 3 independent data dimensions. Je pod doporučeným prahem 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Strojově čitelná data (JSON).
Je Devici bezpečný?
NE — POUŽÍVEJTE S OPATRNOSTÍ — Devici má skóre důvěryhodnosti Nerq 42.5/100 (E). Má podprůměrné signály důvěryhodnosti s významnými mezerami v bezpečnosti, údržbě nebo dokumentaci. Nedoporučeno pro produkční použití bez důkladné ruční kontroly a dalších bezpečnostních opatření.
Jaké je skóre důvěryhodnosti Devici?
Devici má Nerq skóre důvěryhodnosti 42.5/100 se stupněm E. Toto skóre je založeno na 3 nezávisle měřených dimenzích.
Jaká jsou klíčová bezpečnostní zjištění pro Devici?
Nejsilnější signál Devici je údržba na 0/100. Nebyly zjištěny žádné známé zranitelnosti. Dosud nedosáhl ověřeného prahu Nerq 70+.
Co je Devici a kdo jej spravuje?
| Autor | https://github.com/sdelements/devici-mcp |
| Kategorie | bezpečnost |
| Hvězdičky | 4 |
| Zdroj | https://github.com/sdelements/devici-mcp |
Populární alternativy v security
What Is Devici?
Devici is a security tool: Devici manages security 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 security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Devici's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Devici performs in each:
- Údržba (0/100): Devici is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.
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:
- Developers and teams working with security tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Devici. 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 Devici's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Devici's dependency tree. - Recenze permissions — Understand what access Devici requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Devici in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=Devici - Zkontrolujte 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.
- 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 Devici
When evaluating whether Devici is safe, consider these category-specific risks:
Understand how Devici processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Devici's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Devici. Security patches and bug fixes are only effective if you're running the latest version.
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.
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:
Periodically review how Devici is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Devici and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Devici only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Devici's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
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:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional compliance review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Devici 42.5/100 meets your organization's risk tolerance. We recommend running a manual security 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 security 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 security 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 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 maintenance 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 security and quality. Conversely, a downward trend may signal reduced maintenance, 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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Devici are strengthening or weakening over time.
Devici vs Alternatives
V kategorii security, Devici získal skóre 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Devici vs Ciphey — Trust Score: 73.8/100
- Devici vs strix — Trust Score: 73.8/100
- Devici vs SWE-agent — Trust Score: 91.3/100
Hlavní závěry
- Devici má skóre důvěryhodnosti 42.5/100 (E) and is not yet Nerq Verified.
- Devici has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among security tools, Devici scores below the category average of 67/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Často kladené otázky
Je Devici bezpečný k použití?
Jaké je skóre důvěryhodnosti Devici?
Jaké jsou bezpečnější alternativy k Devici?
How often is Devici's safety score updated?
Mohu použít Devici v regulovaném prostředí?
Disclaimer: Skóre důvěryhodnosti Nerq jsou automatizovaná hodnocení založená na veřejně dostupných signálech. Nejsou doporučením ani zárukou. Vždy proveďte vlastní ověření.