@turf/clusters-dbscan
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate automation transition. | ai | |
| phantom-deps | phantom-dep:@types/geokdbush | AI (phantom-deps): @types package providing type declarations; not directly imported at runtime. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Turf.js monorepo; long gaps between major releases are normal for this org. | ai | |
| dependencies | unvetted-dep:@types/geokdbush | AI (dependencies): @types/geokdbush is a TypeScript type definition for geokdbush; low risk, types-only package. | ai | |
| phantom-deps | phantom-dep:@turf/meta | AI (phantom-deps): Same-org scoped package; convention-loaded by turf ecosystem. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Framework-scoped types package; convention-loaded by geospatial libraries. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript transpilation; stable for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 7 / 14 | |
| 7.3.4 | 8 / 13 | |
| 7.3.3 | 8 / 13 | |
| 7.3.2 | 8 / 13 | |
| 7.3.1 | 7 / 14 | |
| 7.3.0 | 7 / 15 | |
| 7.2.0 | 7 / 15 |
v7.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.