jsts
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Same author, no code changes; missing gitHead is benign publish-env variation for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fastpriorityqueue is a legitimate, well-known npm package appropriate for geospatial algorithm performance improvements in a geometry library. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): JSTS stands for JavaScript Topology Suite — a well-known geospatial library with 73 versions and 14 years of history. Not a typosquat of jest; the name similarity is purely coincidental. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 2.12.1 | 1 / 16 | |
| 2.12.0 | 1 / 16 | |
| 2.11.3 | 1 / 19 | |
| 2.11.2 | 0 / 17 | |
| 2.11.1 | 0 / 17 | |
| 2.11.0 | 0 / 17 | |
| 2.10.1 | 0 / 17 | |
| 2.10.0 | 0 / 17 | |
| 2.9.3 | 0 / 17 | |
| 2.9.2 | 0 / 18 | |
| 2.9.1 | 0 / 18 | |
| 2.9.0 | 0 / 18 | |
| 2.8.1 | 0 / 18 | |
| 2.8.0 | 0 / 18 | |
| 2.7.3 | 0 / 17 | |
| 2.7.2 | 0 / 17 | |
| 2.7.1 | 0 / 19 | |
| 2.7.0 | 0 / 18 | |
| 2.6.2 | 0 / 19 | |
| 2.6.1 | 0 / 19 | |
| 2.6.0 | 0 / 19 | |
| 2.5.1 | 0 / 19 | |
| 2.5.0 | 0 / 19 | |
| 2.4.0 | 0 / 19 | |
| 2.3.1 | 0 / 19 | |
| 2.3.0 | 0 / 18 | |
| 2.2.3 | 0 / 23 | |
| 2.2.2 | 0 / 22 | |
| 2.2.1 | 0 / 22 | |
| 2.2.0 | 0 / 22 | |
| 2.1.2 | 0 / 22 | |
| 2.1.1 | 0 / 22 | |
| 2.1.0 | 0 / 23 | |
| 2.0.8 | 0 / 23 | |
| 2.0.7 | 0 / 23 | |
| 2.0.6 | 0 / 23 | |
| 2.0.5 | 0 / 23 | |
| 2.0.4 | 0 / 17 | |
| 2.0.3 | 0 / 18 | |
| 2.0.2 | 0 / 18 | |
| 2.0.1 | 0 / 18 | |
| 2.0.0 | 0 / 17 |
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bjornharrtell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bjornharrtell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.