Is Labelme veilig?

Labelme — Nerq Trust Score 61.4/100 (C-beoordeling). Score gebaseerd op 5 independent trust signals.

Labelme is een software tool met een Nerq Vertrouwensscore van 61.4/100 (C), based on 5 onafhankelijke gegevensdimensies. Beveiliging: 0/100. Onderhoud: 0/100. Populariteit: 0/100. Gegevens afkomstig van meerdere openbare bronnen waaronder pakketregisters, GitHub, NVD, OSV.dev en OpenSSF Scorecard. Laatst bijgewerkt: n/a. Machineleesbare gegevens (JSON).

Is Labelme veilig?

Vertrouwensscore details — Labelme has a Nerq Trust Score of 61.4/100 (C). Measured across 5 independent trust signals.

Beveiligingsanalyse → Labelme Privacyrapport →

Wat is de vertrouwensscore van Labelme?

Labelme heeft een Nerq Trust Score van 61.4/100 met het cijfer C. Deze score is gebaseerd op 5 onafhankelijk gemeten dimensies, waaronder beveiliging, onderhoud en community-adoptie.

Beveiliging
0
Naleving
92
Onderhoud
0
Documentatie
0
Populariteit
0

Wat zijn de belangrijkste beveiligingsbevindingen voor Labelme?

Het sterkste signaal van Labelme is naleving met 92/100. Er zijn geen bekende kwetsbaarheden gedetecteerd.

⚠Beveiligingsscore: 0/100 (zwak)
⚠Onderhoud: 0/100 — lage onderhoudsactiviteit
⚠Naleving: 92/100 — covers 47 of 52 jurisdicties
⚠Documentatie: 0/100 — beperkte documentatie
⚠Populariteit: 0/100 — 15,596 sterren op github

Wat is Labelme en wie onderhoudt het?

OntwikkelaarUnknown
CategorieOther
Sterren15,596
Bronhttps://github.com/wkentaro/labelme

Naleving van regelgeving

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

Populaire alternatieven in 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 beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.

How Nerq Assesses Labelme's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensies. 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 (beveiliging 0/100, onderhoud 0/100, documentatie 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 — Bekijk de repository's beveiliging policy, open issues, and recent commits for signs of active onderhoud.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Labelme's dependency tree.
  3. Beoordeling 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. Bekijk de 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 beveiliging 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. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency beveiliging

Check Labelme's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.

Update frequency

Regularly check for updates to Labelme. Beveiliging 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 naleving

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 naleving with your beveiliging policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for beveiliging advisories

Subscribe to Labelme's beveiliging 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 matig 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 onderhoud 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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, 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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Labelme are strengthening or weakening over time.

Labelme vs Alternatieven

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

Belangrijkste conclusies

Veelgestelde vragen

Is Labelme veilig?
wkentaro/labelme met een Nerq Vertrouwensscore van 61.4/100 (C). Sterkste signaal: naleving (92/100). Score gebaseerd op Beveiliging (0/100), Onderhoud (0/100), Populariteit (0/100), Documentatie (0/100).
Wat is de vertrouwensscore van Labelme?
wkentaro/labelme: 61.4/100 (C). Score gebaseerd op Beveiliging (0/100), Onderhoud (0/100), Populariteit (0/100), Documentatie (0/100). Compliance: 92/100. Scores worden bijgewerkt wanneer nieuwe data beschikbaar komen. API: GET nerq.ai/v1/preflight?target=wkentaro/labelme
Wat zijn veiligere alternatieven voor Labelme?
In de categorie 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.
Hoe vaak wordt de beveiligingsscore van Labelme bijgewerkt?
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
Kan ik Labelme gebruiken in een gereguleerde omgeving?
Labelme: 61.4/100 (C). Compliance: 47 of 52 jurisdicties. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Zie ook

Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.

We gebruiken cookies voor analyse en caching. Privacy