Diabetes Buddy Güvenli mi?

Diabetes Buddy — Nerq Trust Score 55.3/100 (D notu). Puan şuna dayalı: 5 independent trust signals.

Diabetes Buddy bir software tool Nerq Güven Puanı ile 55.3/100 (D), based on 5 bağımsız veri boyutu. Güvenlik: 0/100. Bakım: 1/100. Popülerlik: 0/100. Veriler şuradan alınmıştır: paket kayıtları, GitHub, NVD, OSV.dev ve OpenSSF Scorecard dahil birden fazla genel kaynak. Son güncelleme: n/a. Makine tarafından okunabilir veri (JSON).

Diabetes Buddy Güvenli mi?

Güven Puanı Detayları — Diabetes Buddy has a Nerq Trust Score of 55.3/100 (D). Measured across 5 independent trust signals.

Güvenlik Analizi → Diabetes Buddy Gizlilik Raporu →

Diabetes Buddy'in güven puanı nedir?

Diabetes Buddy'in Nerq Güven Puanı 55.3/100 olup D notu almıştır. Bu puan 5 bağımsız olarak ölçülen boyuta dayanmaktadır.

Güvenlik
0
Uyumluluk
100
Bakım
1
Dokümantasyon
1
Popülerlik
0

Diabetes Buddy için temel güvenlik bulguları nelerdir?

Diabetes Buddy'in en güçlü sinyali 100/100 ile uyumluluk'dir. Bilinen güvenlik açığı tespit edilmemiştir.

⚠Güvenlik puanı: 0/100 (zayıf)
⚠Bakım: 1/100 — düşük bakım etkinliği
⚠Uyumluluk: 100/100 — covers 52 of 52 jurisdictions
⚠Dokümantasyon: 1/100 — sınırlı belgeleme
⚠Popülerlik: 0/100 — topluluk benimsemesi

Diabetes Buddy nedir ve kim tarafından yönetilmektedir?

Geliştiricitheperfectbean
KategoriHealth
Kaynakhttps://github.com/theperfectbean/diabetes-buddy
Frameworksopenai · anthropic · mcp · ollama
Protocolsmcp · rest

Düzenleyici Uyumluluk

EU AI Act Risk ClassMINIMAL
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

health kategorisindeki popüler alternatifler

shibing624/MedicalGPT
52.2/100 · D
github
OpenHealthForAll/open-health
52.2/100 · D
github
FreedomIntelligence/Awesome-AI4Med
50.2/100 · D
github
scutcyr/BianQue
47.0/100 · D
github
huifer/WellAlly-health
49.0/100 · D
github

What Is Diabetes Buddy?

Diabetes Buddy is a software tool in the health category: Diabetes Buddy is an open-source Type 1 Diabetes knowledge partner with a multi-agent RAG architecture and safety features.. Nerq Trust Score: 55/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including güvenlik vulnerabilities, bakım activity, license uyumluluk, and topluluk benimsemesi.

How Nerq Assesses Diabetes Buddy's Safety

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

The overall Trust Score of 55.3/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 Diabetes Buddy?

Diabetes Buddy is commonly evaluated by:

How to read the signals: Diabetes Buddy's measured signals (güvenlik 0/100, bakım 1/100, dokümantasyon 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 Diabetes Buddy's Safety Yourself

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

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

Common Safety Concerns with Diabetes Buddy

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

Data handling

Understand how Diabetes Buddy processes, stores, and transmits your data. İnceleyin tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency güvenlik

Check Diabetes Buddy's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher güvenlik risk.

Update frequency

Regularly check for updates to Diabetes Buddy. Güvenlik patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Diabetes Buddy 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 uyumluluk

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

Diabetes Buddy and the EU AI Act

Diabetes Buddy 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 uyumluluk assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal uyumluluk.

Best Practices for Using Diabetes Buddy Safely

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

Conduct regular audits

Periodically review how Diabetes Buddy is used in your workflow. Check for unexpected behavior, permissions drift, and uyumluluk with your güvenlik policies.

Keep dependencies updated

Ensure Diabetes Buddy and all its dependencies are running the latest stable versions to benefit from güvenlik patches.

Follow least privilege

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

Monitor for güvenlik advisories

Subscribe to Diabetes Buddy's güvenlik 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 Diabetes Buddy is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Diabetes Buddy

Nerq's signals are one input. In the following situations, evaluate Diabetes Buddy's measured signals against your own requirements before making a decision:

For each situation, compare Diabetes Buddy's measured trust score of 55.3/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Diabetes Buddy is suitable for any particular use.

How Diabetes Buddy Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among health tools, the average Trust Score is 62/100. Diabetes Buddy's score of 55.3/100 is near the category average of 62/100.

This places Diabetes Buddy in line with the typical health tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks orta 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 Diabetes Buddy 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 bakım patterns change, Diabetes Buddy'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 güvenlik and quality. Conversely, a downward trend may signal reduced bakım, growing technical debt, or unresolved vulnerabilities. To track Diabetes Buddy's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=diabetes-buddy&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 — güvenlik, bakım, dokümantasyon, uyumluluk, and community — has evolved independently, providing granular visibility into which aspects of Diabetes Buddy are strengthening or weakening over time.

Diabetes Buddy vs Alternatifler

In the health category, Diabetes Buddy scores 55.3/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Temel Çıkarımlar

Sık Sorulan Sorular

Diabetes Buddy Güvenli mi?
diabetes-buddy Nerq Güven Puanı ile 55.3/100 (D). En güçlü sinyal: uyumluluk (100/100). Puan şuna dayalı: Güvenlik (0/100), Bakım (1/100), Popülerlik (0/100), Dokümantasyon (1/100).
Diabetes Buddy'in güven puanı nedir?
diabetes-buddy: 55.3/100 (D). Puan şuna dayalı: Güvenlik (0/100), Bakım (1/100), Popülerlik (0/100), Dokümantasyon (1/100). Compliance: 100/100. Yeni veriler mevcut olduğunda puanlar güncellenir. API: GET nerq.ai/v1/preflight?target=diabetes-buddy
Diabetes Buddy için daha güvenli alternatifler nelerdir?
Health kategorisinde, higher-rated alternatives include shibing624/MedicalGPT (52/100), OpenHealthForAll/open-health (52/100), FreedomIntelligence/Awesome-AI4Med (50/100). diabetes-buddy scores 55.3/100.
Diabetes Buddy güvenlik puanı ne sıklıkla güncellenir?
Nerq recomputes Diabetes Buddy's trust score as new data becomes available. Current: 55.3/100 (D). API: GET nerq.ai/v1/preflight?target=diabetes-buddy
Diabetes Buddy'i düzenlenmiş bir ortamda kullanabilir miyim?
Diabetes Buddy: 55.3/100 (D). Compliance: 52 of 52 jurisdictions. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Ayrıca bakınız

Disclaimer: Nerq güven puanları, kamuya açık sinyallere dayanan otomatik değerlendirmelerdir. Tavsiye veya garanti niteliğinde değildir. Her zaman kendi doğrulamanızı yapın.

Analiz ve önbelleğe alma için çerezler kullanıyoruz. Gizlilik