bin-check
Check if a binary is working
bin-check@4.1.0 was published on 2017-06-20. 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 bin-check versions · Permanent reference to 4.1.0
Package specifications
| Version | 4.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-06-20T17:55:07.064Z |
| 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 | 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 | 18 |
| Repository stars | 13 |
| Repository forks | 4 |
Install bin-check 4.1.0
npm install bin-check@4.1.0 pnpm add bin-check@4.1.0 yarn add bin-check@4.1.0
Runtime dependencies
- execa ^0.7.0
- executable ^4.1.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.
- cross-spawn@5.1.0 — indirect
- execa@0.7.0 — direct
- executable@4.1.1 — direct
- get-stream@3.0.0 — indirect
- is-stream@1.1.0 — indirect
- isexe@2.0.0 — indirect
- lru-cache@4.1.5 — indirect
- npm-run-path@2.0.2 — indirect
- p-finally@1.0.0 — indirect
- path-key@2.0.1 — indirect
- pify@2.3.0 — indirect
- pseudomap@1.0.2 — indirect
- shebang-command@1.2.0 — indirect
- shebang-regex@1.0.0 — indirect
- signal-exit@3.0.7 — indirect
- strip-eof@1.0.0 — indirect
- which@1.3.1 — indirect
- yallist@2.1.2 — indirect
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/30 approved changesets -- score normalized to 0 |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 7/10 — binaries present in source code |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/bin-check/4.1.0 — retrieved 2026-10-29T10:59:32.037Z
- https://api.deps.dev/v3/projects/github.com%2Fkevva%2Fbin-check — retrieved 2026-10-29T10:59:32.681Z
- https://api.deps.dev/v3/systems/npm/packages/bin-check/versions/4.1.0 — retrieved 2026-10-29T11:13:23.335Z
- https://api.deps.dev/v3/systems/npm/packages/bin-check/versions/4.1.0:dependencies — retrieved 2026-10-29T11:13:23.368Z