safe-buffer and the Cyber Resilience Act
3 of 8 readable security signals are in place for safe-buffer 5.2.1 (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: MIT (component documentation and licence notices)
- missingCode review before merge: Scorecard Code-Review 1/10 (secure development process (Annex VII, development and vulnerability handling processes))
- unknownCI workflow hygiene: no Scorecard data (integrity of the build and update chain)
- missingSigned releases or provenance: not assessed (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)
safe-buffer 5.2.1 is the current default version of this npm package, published on 2020-05-10. The registry lists 11 versions in total and the licence declared is MIT. The source repository is feross/safe-buffer with 345 stars.
The OpenSSF Scorecard for the repository was last computed on 2026-08-24 and gives an overall 2.5/10. Signals that are not in place today: actively maintained; security policy; code review before merge; signed releases or provenance; automated security testing. 1 signal is unknown because the data is not published.
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 safe-buffer, 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 safe-buffer 5.2.1 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 feross/safe-buffer, or check your own SBOM and create the licence notices.
More in the index
inherits, which, fast-json-stable-stringify, uri-js, is-number, import-fresh · 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; unknown means the data is not published.
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.