vt-pbf
Serialize mapbox vector tiles to binary protobufs in javascript.
vt-pbf@3.1.3 was published on 2021-06-07. Its manifest declares 3 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 vt-pbf versions · Permanent reference to 3.1.3
Package specifications
| Version | 3.1.3 |
|---|---|
| License declaration | MIT |
| Published | 2021-06-07T09:18:29.469Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 11.71 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 206 |
| Repository forks | 37 |
Install vt-pbf 3.1.3
npm install vt-pbf@3.1.3 pnpm add vt-pbf@3.1.3 yarn add vt-pbf@3.1.3
Runtime dependencies
- @mapbox/point-geometry 0.1.0
- @mapbox/vector-tile ^1.3.1
- pbf ^3.2.1
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.
- @mapbox/point-geometry@0.1.0 — direct
- @mapbox/vector-tile@1.3.1 — direct
- ieee754@1.2.1 — indirect
- pbf@3.3.0 — direct
- protocol-buffers-schema@3.6.1 — indirect
- resolve-protobuf-schema@2.1.0 — 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 | 5/10 — Found 13/26 approved changesets -- score normalized to 5 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 8/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/vt-pbf/3.1.3 — retrieved 2026-10-29T11:31:20.865Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/vt-pbf/versions/3.1.3:dependencies — retrieved 2026-10-29T07:10:49.676Z
- https://api.deps.dev/v3/systems/npm/packages/vt-pbf/versions/3.1.3 — retrieved 2026-10-29T07:10:49.641Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fmapbox%2Fvt-pbf — retrieved 2026-10-29T07:10:49.147Z (stale snapshot; refresh pending)