terraformer-wkt-parser 0.1.3
Well-Known Text parser
terraformer-wkt-parser@0.1.3 was published on 2013-01-24. Its manifest declares 1 runtime dependency 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: terraformer-wkt-parser is deprecated and no longer supported. Please use @terraformer/wkt.
All terraformer-wkt-parser versions · Permanent reference to 0.1.3 · Latest release
Package specifications
| Version | 0.1.3 |
|---|---|
| License declaration | MIT |
| Published | 2013-01-24T18:14:29.204Z |
| Node.js requirement | Not declared |
| 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 | 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 | 2 |
| Repository stars | 80 |
| Repository forks | 30 |
Install terraformer-wkt-parser 0.1.3
npm install terraformer-wkt-parser@0.1.3 pnpm add terraformer-wkt-parser@0.1.3 yarn add terraformer-wkt-parser@0.1.3
Runtime dependencies
- terraformer latest
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.
- @types/geojson@7946.0.16 — indirect
- terraformer@1.0.12 — 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 | 0/10 — project is archived |
|---|---|
| Code-Review | 2/10 — Found 5/21 approved changesets -- score normalized to 2 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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 |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/terraformer-wkt-parser/0.1.3 — retrieved 2026-10-31T16:10:07.839Z
- https://api.deps.dev/v3/projects/github.com%2FEsri%2Fterraformer-wkt-parser — retrieved 2026-10-31T16:09:26.352Z
- https://api.deps.dev/v3/systems/npm/packages/terraformer-wkt-parser/versions/0.1.3 — retrieved 2026-10-31T16:10:08.317Z
- https://api.deps.dev/v3/systems/npm/packages/terraformer-wkt-parser/versions/0.1.3:dependencies — retrieved 2026-10-31T16:10:08.351Z