@types/topojson-server
TypeScript definitions for topojson-server
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Type-only package; @types/geojson types are re-exported by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/topojson-specification | AI (phantom-deps): Type-only package; @types/topojson-specification types are re-exported by convention, not directly imported. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 2 / 0 | |
| 3.0.3 | 2 / 0 | |
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 |
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.