is-binary-buffer 2.0.0
Returns true if a buffer is binary. Takes a buffer and does not read from the file system.
is-binary-buffer@2.0.0 was published on 2018-03-07. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.
All is-binary-buffer versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-03-07T12:13:17.048Z |
| Node.js requirement | >=4 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 5.50 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 5 |
| Repository forks | 0 |
Install is-binary-buffer 2.0.0
npm install is-binary-buffer@2.0.0 pnpm add is-binary-buffer@2.0.0 yarn add is-binary-buffer@2.0.0
Runtime dependencies
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- file-type@7.7.1 — direct
- kind-of@6.0.3 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 0/10 — Found 0/7 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| SAST | 0/10 — no SAST tool detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/is-binary-buffer/2.0.0 — retrieved 2026-10-29T21:52:35.425Z
- https://api.deps.dev/v3/systems/npm/packages/is-binary-buffer/versions/2.0.0:dependencies — retrieved 2026-10-29T21:25:44.800Z
- https://api.deps.dev/v3/systems/npm/packages/is-binary-buffer/versions/2.0.0 — retrieved 2026-10-29T21:25:44.786Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fis-binary-buffer — retrieved 2026-10-29T21:13:14.032Z