@turf/line-offset
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.js migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected publisher for all future versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): tslib is a standard TypeScript runtime helper; its addition reflects the monorepo's TS build tooling, not a supply-chain attack. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dependency; not directly imported but required by compiled output. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/geojson is a type-only dependency used by convention in GeoJSON-based packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 5 / 11 | |
| 7.3.4 | 5 / 10 | |
| 7.3.3 | 5 / 10 | |
| 7.3.2 | 5 / 10 | |
| 7.3.1 | 4 / 9 | |
| 7.3.0 | 4 / 10 |
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.