¿Es Db Doctor Seguro?

Db Doctor — Nerq Trust Score 52.0/100 (Grado D). Puntuación basada en 5 independent trust signals.

Db Doctor es un software tool con un Nerq Trust Score de 52.0/100 (D), basado en 5 dimensiones de datos independientes. Seguridad: 0/100. Mantenimiento: 1/100. Popularidad: 0/100. Datos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Última actualización: n/a. Datos legibles por máquina (JSON).

¿Es Db Doctor Seguro?

Desglose de Puntuación de Confianza — Db Doctor has a Nerq Trust Score of 52.0/100 (D). Measured across 5 independent trust signals.

Análisis de Seguridad → Informe de Privacidad de Db Doctor →

¿Cuál es la puntuación de confianza de Db Doctor?

Db Doctor tiene una Puntuación de Confianza Nerq de 52.0/100, obteniendo un grado D. Esta puntuación se basa en 5 dimensiones medidas independientemente.

Seguridad
0
Cumplimiento
48
Mantenimiento
1
Documentación
1
Popularidad
0

¿Cuáles son los hallazgos de seguridad clave de Db Doctor?

La señal más fuerte de Db Doctor es cumplimiento con 48/100. No se han detectado vulnerabilidades conocidas.

⚠Puntuación de seguridad: 0/100 (débil)
⚠Mantenimiento: 1/100 — baja actividad de mantenimiento
⚠Cumplimiento: 48/100 — covers 24 of 52 jurisdictions
⚠Documentación: 1/100 — documentación limitada
⚠Popularidad: 0/100 — 1 estrellas en github

¿Qué es Db Doctor y quién lo mantiene?

Autorhanpf2391
CategoríaData
Estrellas1
Fuentehttps://github.com/hanpf2391/DB-Doctor
Frameworkslangchain · openai · anthropic · ollama
Protocolsrest

Cumplimiento Regulatorio

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

Alternativas Populares en data

firecrawl/firecrawl
64.4/100 · C
github
MinerU
76.6/100 · B
github
mindsdb/mindsdb
68.1/100 · C
github
PostHog
48.9/100 · D
pulsemcp
Graphiti
48.9/100 · D
pulsemcp

What Is Db Doctor?

Db Doctor is a software tool in the data category: DB-Doctor 是一个基于 DeepSeek/LLM 的 MySQL 慢查询智能诊疗系统。. It has 1 GitHub stars. Nerq Trust Score: 52/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including seguridad vulnerabilities, mantenimiento activity, license cumplimiento, and adopción por la comunidad.

How Nerq Assesses Db Doctor's Safety

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

The overall Trust Score of 52.0/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 Db Doctor?

Db Doctor is commonly evaluated by:

How to read the signals: Db Doctor's measured signals (seguridad 0/100, mantenimiento 1/100, documentación 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 Db Doctor's Safety Yourself

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

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

Common Safety Concerns with Db Doctor

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

Data handling

Understand how Db Doctor processes, stores, and transmits your data. Revisar el/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency seguridad

Check Db Doctor's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher seguridad risk.

Update frequency

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

Third-party integrations

If Db Doctor 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 cumplimiento

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

Db Doctor and the EU AI Act

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

Best Practices for Using Db Doctor Safely

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

Conduct regular audits

Periodically review how Db Doctor is used in your workflow. Check for unexpected behavior, permissions drift, and cumplimiento with your seguridad policies.

Keep dependencies updated

Ensure Db Doctor and all its dependencies are running the latest stable versions to benefit from seguridad patches.

Follow least privilege

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

Monitor for seguridad advisories

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

Situations That Warrant Independent Review of Db Doctor

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

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

How Db Doctor Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among data tools, the average Trust Score is 62/100. Db Doctor's score of 52.0/100 is below the category average of 62/100.

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

Db Doctor vs Alternativas

In the data category, Db Doctor scores 52.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Puntos Clave

Preguntas Frecuentes

¿Es Db Doctor Seguro?
DB-Doctor con un Nerq Trust Score de 52.0/100 (D). Señal más fuerte: cumplimiento (48/100). Puntuación basada en Seguridad (0/100), Mantenimiento (1/100), Popularidad (0/100), Documentación (1/100).
¿Cuál es la puntuación de confianza de Db Doctor?
DB-Doctor: 52.0/100 (D). Puntuación basada en Seguridad (0/100), Mantenimiento (1/100), Popularidad (0/100), Documentación (1/100). Compliance: 48/100. Las puntuaciones se actualizan cuando hay nuevos datos. API: GET nerq.ai/v1/preflight?target=DB-Doctor
¿Cuáles son alternativas más seguras a Db Doctor?
En la categoría Data, higher-rated alternatives include firecrawl/firecrawl (64/100), MinerU (77/100), mindsdb/mindsdb (68/100). DB-Doctor scores 52.0/100.
¿Con qué frecuencia se actualiza la puntuación de Db Doctor?
Nerq recomputes Db Doctor's trust score as new data becomes available. Current: 52.0/100 (D). API: GET nerq.ai/v1/preflight?target=DB-Doctor
¿Puedo usar Db Doctor en un entorno regulado?
Db Doctor: 52.0/100 (D). Compliance: 24 of 52 jurisdictions. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Ver también

Disclaimer: Las puntuaciones de confianza de Nerq son evaluaciones automatizadas basadas en señales disponibles públicamente. No son respaldos ni garantías. Siempre realice su propia diligencia debida.

Usamos cookies para análisis y caché. Privacidad