Boddi est-il sûr ?
Boddi — Nerq Trust Score 49.5/100 (Note D). Score basé sur 5 independent trust signals.
Boddi est un software tool avec un Nerq Trust Score de 49.5/100 (D), basé sur 5 dimensions de données indépendantes. Sécurité: 0/100. Maintenance: 1/100. Popularité: 0/100. Données de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Dernière mise à jour: n/a. Données lisibles par machine (JSON).
Boddi est-il sûr ?
Détail du score de confiance — Boddi has a Nerq Trust Score of 49.5/100 (D). Measured across 5 independent trust signals.
Quel est le score de confiance de Boddi ?
Boddi a un Score de Confiance Nerq de 49.5/100, obtenant la note D. Ce score est basé sur 5 dimensions mesurées indépendamment.
Quels sont les résultats de sécurité clés pour Boddi ?
Le signal le plus fort de Boddi est conformité à 99/100. Aucune vulnérabilité connue n'a été détectée.
Qu'est-ce que Boddi et qui le maintient ?
| Auteur | Rktim |
| Catégorie | Communication |
| Source | https://github.com/Rktim/Boddi |
| Frameworks | ollama |
| Protocols | rest |
Conformité réglementaire
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 99/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Alternatives populaires dans communication
What Is Boddi?
Boddi is a software tool in the communication category: A local-first, open-source agentic AI companion with real-time voice interaction and expressive visuals.. Nerq Trust Score: 50/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sécurité vulnerabilities, maintenance activity, license conformité, and adoption par la communauté.
How Nerq Assesses Boddi's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Boddi performs in each:
- Sécurité (0/100): Boddi's sécurité posture is poor. This score factors in known CVEs, dependency vulnerabilities, sécurité policy presence, and code signing practices.
- Maintenance (1/100): Boddi is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
- Compliance (99/100): Boddi is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Basé sur GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 49.5/100 (D) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.
Who Typically Evaluates Boddi?
Boddi is commonly evaluated by:
- Developers and teams working with communication tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Boddi's measured signals (sécurité 0/100, maintenance 1/100, documentation 1/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.
How to Verify Boddi's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Examiner le/la repository's sécurité 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 Boddi's dependency tree. - Avis permissions — Understand what access Boddi requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Boddi 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=Boddi - Examiner le/la license — Confirm that Boddi'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Boddi
When evaluating whether Boddi is safe, consider these category-specific risks:
Understand how Boddi processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Boddi's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.
Regularly check for updates to Boddi. Sécurité patches and bug fixes are only effective if you're running the latest version.
If Boddi 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 Boddi's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Boddi in violation of its license can expose your organization to legal liability.
Boddi and the EU AI Act
Boddi is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.
Nerq's conformité assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal conformité.
Best Practices for Using Boddi Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Boddi while minimizing risk:
Periodically review how Boddi is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.
Ensure Boddi and all its dependencies are running the latest stable versions to benefit from sécurité patches.
Grant Boddi only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Boddi's sécurité advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Boddi is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Boddi
Nerq's signals are one input. In the following situations, evaluate Boddi's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Boddi's measured trust score of 49.5/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Boddi is suitable for any particular use.
How Boddi Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among communication tools, the average Trust Score is 62/100. Boddi's score of 49.5/100 is below the category average of 62/100.
This suggests that Boddi trails behind many comparable communication tools. Organizations with strict sécurité 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 modéré 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 Boddi 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, Boddi'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 sécurité and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Boddi's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Boddi&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 — sécurité, maintenance, documentation, conformité, and community — has evolved independently, providing granular visibility into which aspects of Boddi are strengthening or weakening over time.
Boddi vs Alternatives
In the communication category, Boddi scores 49.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Boddi vs Real-Time-Voice-Cloning — Trust Score: 56.9/100
- Boddi vs ChatGPT — Trust Score: 59.4/100
- Boddi vs jan — Trust Score: 64.4/100
Points Essentiels
- Boddi has a measured Nerq Trust Score of 49.5/100 (D) — a composite of independent signals, not a suitability judgment.
- Among communication tools, Boddi scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — sécurité, maintenance, documentation, conformité, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Questions fréquentes
Boddi est-il sûr ?
Quel est le score de confiance de Boddi ?
Quelles sont les alternatives plus sûres à Boddi ?
À quelle fréquence le score de sécurité de Boddi est-il mis à jour ?
Puis-je utiliser Boddi dans un environnement réglementé ?
Voir aussi
Disclaimer: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.