pbf 1.3.2
a low-level, lightweight protocol buffers implementation in JavaScript
pbf@1.3.2 was published on 2015-03-05. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All pbf versions · Permanent reference to 1.3.2 · Latest release
Package specifications
| Version | 1.3.2 |
|---|---|
| License declaration | BSD |
| Published | 2015-03-05T17:06:54.012Z |
| Node.js requirement | Not declared |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 886 |
| Repository forks | 113 |
Install pbf 1.3.2
npm install pbf@1.3.2 pnpm add pbf@1.3.2 yarn add pbf@1.3.2
Runtime dependencies
- ieee754 ~1.1.4
- resolve-protobuf-schema ^1.0.2
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.
- ieee754@1.1.13 — direct
- protobuf-schema@1.5.1 — indirect
- resolve-protobuf-schema@1.0.2 — 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.
| Maintained | 10/10 — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| Code-Review | 4/10 — Found 6/14 approved changesets -- score normalized to 4 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| 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 | 6/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 9/10 — SAST tool is not run on all commits -- score normalized to 9 |
Evidence and freshness
- https://registry.npmjs.org/pbf/1.3.2 — retrieved 2026-10-29T08:31:42.889Z
- https://api.deps.dev/v3/projects/github.com%2Fmapbox%2Fpbf — retrieved 2026-10-29T07:09:23.323Z
- https://api.deps.dev/v3/systems/npm/packages/pbf/versions/1.3.2 — retrieved 2026-10-29T08:31:43.486Z
- https://api.deps.dev/v3/systems/npm/packages/pbf/versions/1.3.2:dependencies — retrieved 2026-10-29T08:31:43.559Z