topojson 0.0.21
An extension to GeoJSON that encodes topology.
topojson@0.0.21 was published on 2013-02-26. 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.
Deprecated: Use topojson-client, topojson-server or topojson-simplify directly.
All topojson versions · Permanent reference to 0.0.21 · Latest release
Package specifications
| Version | 0.0.21 |
|---|---|
| License declaration | Not declared |
| Published | 2013-02-26T05:23:39.827Z |
| 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 | 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 | 5 |
| Repository stars | 4906 |
| Repository forks | 683 |
Install topojson 0.0.21
npm install topojson@0.0.21 pnpm add topojson@0.0.21 yarn add topojson@0.0.21
Runtime dependencies
- optimist 0.3.x
- queue-async 1.0.x
- shapefile 0.0.x
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.
- iconv-lite@0.2.11 — indirect
- optimist@0.3.7 — direct
- queue-async@1.0.7 — direct
- shapefile@0.0.11 — direct
- wordwrap@0.0.3 — 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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 1/10 — Found 3/30 approved changesets -- score normalized to 1 |
| 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 | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/topojson/0.0.21 — retrieved 2026-10-29T10:43:50.194Z
- https://api.deps.dev/v3/projects/github.com%2Ftopojson%2Ftopojson — retrieved 2026-10-29T08:16:49.329Z
- https://api.deps.dev/v3/systems/npm/packages/topojson/versions/0.0.21 — retrieved 2026-10-29T10:43:50.708Z
- https://api.deps.dev/v3/systems/npm/packages/topojson/versions/0.0.21:dependencies — retrieved 2026-10-29T10:43:50.729Z