¿Es Labelme Seguro?

Labelme — Nerq Trust Score 61.4/100 (Grado C). Puntuación basada en 5 independent trust signals.

Labelme es un software tool con un Nerq Trust Score de 61.4/100 (C), basado en 5 dimensiones de datos independientes. Seguridad: 0/100. Mantenimiento: 0/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 Labelme Seguro?

Desglose de Puntuación de Confianza — Labelme has a Nerq Trust Score of 61.4/100 (C). Measured across 5 independent trust signals.

Análisis de Seguridad → Informe de Privacidad de Labelme →

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

Labelme tiene una Puntuación de Confianza Nerq de 61.4/100, obteniendo un grado C. Esta puntuación se basa en 5 dimensiones medidas independientemente.

Seguridad
0
Cumplimiento
92
Mantenimiento
0
Documentación
0
Popularidad
0

¿Cuáles son los hallazgos de seguridad clave de Labelme?

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

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

¿Qué es Labelme y quién lo mantiene?

AutorUnknown
CategoríaOther
Estrellas15,596
Fuentehttps://github.com/wkentaro/labelme

Cumplimiento Regulatorio

EU AI Act Risk ClassNot assessed
Compliance Score92/100
JurisdictionsAssessed across 52 jurisdictions

Alternativas Populares en other

Developer-Y/cs-video-courses
59.9/100 · D
github
binhnguyennus/awesome-scalability
59.4/100 · D
github
obra/superpowers
62.4/100 · C
github
ultralytics/yolov5
61.4/100 · C
github
deepfakes/faceswap
56.9/100 · D
github

What Is Labelme?

Labelme is a software tool in the other category: Image Polygonal Annotation with Python (polygon, rectangle, circle, line, point and image-level flag annotation).. It has 15,596 GitHub stars. Nerq Trust Score: 61/100 (C).

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 Labelme's Safety

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

The overall Trust Score of 61.4/100 (C) 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 Labelme?

Labelme is commonly evaluated by:

How to read the signals: Labelme's measured signals (seguridad 0/100, mantenimiento 0/100, documentación 0/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 Labelme'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 Labelme's dependency tree.
  3. Reseña permissions — Understand what access Labelme requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Labelme 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=wkentaro/labelme
  6. Revisar el/la license — Confirm that Labelme'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 Labelme

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

Data handling

Understand how Labelme 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 Labelme's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher seguridad risk.

Update frequency

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

Third-party integrations

If Labelme 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 Labelme's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Labelme in violation of its license can expose your organization to legal liability.

Best Practices for Using Labelme Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for seguridad advisories

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

Situations That Warrant Independent Review of Labelme

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

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

How Labelme Compares to Industry Standards

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

This places Labelme in line with the typical other 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 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 Labelme 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, Labelme'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 Labelme's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=wkentaro/labelme&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 Labelme are strengthening or weakening over time.

Labelme vs Alternativas

In the other category, Labelme scores 61.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Puntos Clave

Preguntas Frecuentes

¿Es Labelme Seguro?
wkentaro/labelme con un Nerq Trust Score de 61.4/100 (C). Señal más fuerte: cumplimiento (92/100). Puntuación basada en Seguridad (0/100), Mantenimiento (0/100), Popularidad (0/100), Documentación (0/100).
¿Cuál es la puntuación de confianza de Labelme?
wkentaro/labelme: 61.4/100 (C). Puntuación basada en Seguridad (0/100), Mantenimiento (0/100), Popularidad (0/100), Documentación (0/100). Compliance: 92/100. Las puntuaciones se actualizan cuando hay nuevos datos. API: GET nerq.ai/v1/preflight?target=wkentaro/labelme
¿Cuáles son alternativas más seguras a Labelme?
En la categoría Other, higher-rated alternatives include Developer-Y/cs-video-courses (60/100), binhnguyennus/awesome-scalability (59/100), obra/superpowers (62/100). wkentaro/labelme scores 61.4/100.
¿Con qué frecuencia se actualiza la puntuación de Labelme?
Nerq recomputes Labelme's trust score as new data becomes available. Current: 61.4/100 (C). API: GET nerq.ai/v1/preflight?target=wkentaro/labelme
¿Puedo usar Labelme en un entorno regulado?
Labelme: 61.4/100 (C). Compliance: 47 of 52 jurisdictions. 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