@turf/tin
Takes a set of points and creates a Triangulated Irregular Network.
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): Turf monorepo migrated to GitHub Actions publishing; SLSA attestation confirms CI/CD origin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-published release with SLSA provenance; consistent with monorepo release cadence. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): @turf/tin is a legitimate Turfjs monorepo package; no relation to pino. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit dependency pattern is expected. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/geojson is a type-only dependency loaded by convention in GeoJSON-based packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 3 / 7 | |
| 7.3.4 | 3 / 7 | |
| 7.3.3 | 3 / 7 | |
| 7.3.2 | 3 / 7 | |
| 7.3.1 | 3 / 7 | |
| 7.3.0 | 3 / 8 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.