is-binary-path 1.0.0
Check if a filepath is a binary file
is-binary-path@1.0.0 was published on 2015-01-24. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All is-binary-path versions · Permanent reference to 1.0.0 · Latest release
Package specifications
| Version | 1.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2015-01-24T09:13:13.344Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 49 |
| Repository forks | 8 |
Install is-binary-path 1.0.0
npm install is-binary-path@1.0.0 pnpm add is-binary-path@1.0.0 yarn add is-binary-path@1.0.0
Runtime dependencies
- binary-extensions ^1.0.0
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.
- binary-extensions@1.13.1 — 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 | 1/10 — Found 4/22 approved changesets -- score normalized to 1 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/is-binary-path/1.0.0 — retrieved 2026-10-29T10:21:13.765Z
- https://api.deps.dev/v3/projects/github.com%2Fsindresorhus%2Fis-binary-path — retrieved 2026-10-29T07:15:05.310Z
- https://api.deps.dev/v3/systems/npm/packages/is-binary-path/versions/1.0.0:dependencies — retrieved 2026-10-29T10:21:14.378Z
- https://api.deps.dev/v3/systems/npm/packages/is-binary-path/versions/1.0.0 — retrieved 2026-10-29T10:21:14.370Z