binary-parser 1.3.3
Blazing-fast binary parser builder
binary-parser@1.3.3 was published on 2019-06-02. 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 >=5.10.0.
Deprecated: TypeScript interface is broken in this version
All binary-parser versions · Permanent reference to 1.3.3 · Latest release
Package specifications
| Version | 1.3.3 |
|---|---|
| License declaration | MIT |
| Published | 2019-06-02T08:57:36.070Z |
| Node.js requirement | >=5.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 | 101.24 KiB |
| Published file count | 15 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | dist/binary_parser.js |
| Side effects declaration | Not declared |
| Direct advisories | 1 |
| Resolved graph dependencies | 12 |
| Repository stars | 955 |
| Repository forks | 142 |
Install binary-parser 1.3.3
npm install binary-parser@1.3.3 pnpm add binary-parser@1.3.3 yarn add binary-parser@1.3.3
Runtime dependencies
- mocha-junit-reporter ^1.22.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.
- ansi-regex@3.0.1 — indirect
- charenc@0.0.2 — indirect
- crypt@0.0.2 — indirect
- debug@2.6.9 — indirect
- is-buffer@1.1.6 — indirect
- md5@2.3.0 — indirect
- minimist@1.2.8 — indirect
- mkdirp@0.5.6 — indirect
- mocha-junit-reporter@1.23.3 — direct
- ms@2.0.0 — indirect
- strip-ansi@4.0.0 — indirect
- xml@1.0.1 — 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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 2/10 — Found 2/7 approved changesets -- score normalized to 2 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 8/10 — binaries present in source code |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 2/10 — dependency not pinned by hash detected -- score normalized to 2 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 9/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/binary-parser/1.3.3 — retrieved 2026-11-01T07:53:59.068Z
- https://api.deps.dev/v3/systems/npm/packages/binary-parser/versions/1.3.3 — retrieved 2026-11-01T07:53:59.552Z
- https://api.deps.dev/v3/systems/npm/packages/binary-parser/versions/1.3.3:dependencies — retrieved 2026-11-01T07:53:59.573Z
- https://api.deps.dev/v3/projects/github.com%2Fkeichi%2Fbinary-parser — retrieved 2026-11-01T07:53:59.943Z