</>PackageGraphPackageGraph

safer-buffer

npmv2.1.2

Modern Buffer API polyfill without footguns

Not recommended for new projects

No — safer-buffer should not be adopted for new projects. Last published 3076 days ago.

  • AAdoption: grade A, Excellent.

    110.7M downloads per week and 5 known dependents.

  • FMaintenance: grade F, Failing.

    Last published 3076 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 41 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding safer-buffer to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

41 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Dependencies

Declared by safer-buffer v2.1.2. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (2)

standard ^11.0.1tape ^4.9.0

Used by

Popular packages that depend on safer-buffer.

Relationship graph

Dependencies (left) and dependents (right) of safer-buffer.

asn1qsiconv-liteobject-inspectsshpksafer-buffer
safer-buffer dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 1 day apart.

Recent versions of safer-buffer
VersionPublishedSizeLicense
2.1.2latest8 years ago41 KBMIT
2.1.18 years ago41 KBMIT
2.1.08 years ago40 KBMIT
2.0.28 years ago36 KBMIT
2.0.18 years ago21 KBMIT
2.0.08 years ago19 KBMIT

Overview

safer-buffer is an npm package that modern Buffer API polyfill without footguns. It is extremely widely used, with about 110.7M downloads per week and 5 known dependents in the graph. The latest version is 2.1.2, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need modern Buffer API polyfill without footguns and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (110.7M weekly downloads).
  • Clear open-source license (MIT).
  • Lean dependency tree (2 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Frequently asked questions

Should I use safer-buffer?

No — safer-buffer should not be adopted for new projects. Last published 3076 days ago.

How do I install safer-buffer?

Run `npm install safer-buffer` to add safer-buffer to your npm project.

What license is safer-buffer released under?

safer-buffer is distributed under the MIT license.

How popular is safer-buffer?

safer-buffer has approximately 110,736,744 downloads per week and 5 known dependent packages.

Is safer-buffer still maintained?

The most recent release of safer-buffer (v2.1.2) was published 8 years ago.

Does safer-buffer run install scripts?

No. safer-buffer does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.