detect-libc and the Cyber Resilience Act
5 of 9 readable security signals are in place for detect-libc 2.1.2 (npm). Data checked 2026-10-05.
- passNo known vulnerabilities in the latest version: none listed (Annex I, Part II: address and remediate vulnerabilities without delay)
- passNot deprecated: not marked as deprecated (support period and updates)
- missingActively maintained: Scorecard Maintained 0/10 (security updates for the whole support period)
- missingSecurity policy: Scorecard Security-Policy 0/10 (Annex I, Part II: coordinated vulnerability disclosure policy and contact address)
- passLicence declared: Apache-2.0 (component documentation and licence notices)
- missingCode review before merge: Scorecard Code-Review 2/10 (secure development process (Annex VII, development and vulnerability handling processes))
- passCI workflow hygiene: Dangerous-Workflow 10, Token-Permissions 10 (integrity of the build and update chain)
- passSigned releases or provenance: build provenance or attestations published (Annex I, Part II: secure distribution of updates)
- missingAutomated security testing: SAST 0, Fuzzing 0 (Annex I, Part II: effective and regular tests and reviews)
detect-libc 2.1.2 is the current default version of this npm package, published on 2025-10-05. The registry lists 23 versions in total and the licence declared is Apache-2.0. The source repository is lovell/detect-libc with 78 stars.
The OpenSSF Scorecard for the repository was last computed on 2026-08-24 and gives an overall 3.8/10. Signals that are not in place today: actively maintained; security policy; code review before merge; automated security testing.
As of 2026-10-05, deps.dev lists no known advisories for this version. That is a snapshot and not a promise: new advisories can be published at any time.
If you ship a product that includes detect-libc, the Cyber Resilience Act expects you to know which components you ship, to follow their vulnerabilities and to exercise due diligence on third-party components (Annex I, Part II and Article 13). In practice: list detect-libc 2.1.2 in your SBOM with its package URL pkg:npm/[email protected], watch for new advisories, and note that you have no published security contact upstream, so plan how you would report a problem. With several signals missing, consider whether a better-maintained alternative exists.
Put the badge in your README
Check your own project
Run the repository check on lovell/detect-libc, or check your own SBOM and create the licence notices.
More in the index
glob-parent, p-locate, locate-path, fill-range, path-parse, @jridgewell/trace-mapping · all npm packages
Sources and method
Package and version facts, licences, advisories and provenance: deps.dev (generated data under CC BY 4.0; advisories from OSV). Repository signals: the OpenSSF Scorecard. We read them on 2026-10-05 and show them without scoring the people behind a project. The nine signals are our selection; every signal could be read for this package.
Information generated from your inputs, with article references to Regulation (EU) 2024/2847. It is not legal advice and does not replace your own assessment; check the references against the Official Journal.