@luomus/laji-map
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript @types packages are convention-loaded; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): TypeScript @types packages are convention-loaded; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/leaflet | AI (phantom-deps): TypeScript @types packages are convention-loaded; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/leaflet-draw | AI (phantom-deps): TypeScript @types packages are convention-loaded; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/proj4leaflet | AI (phantom-deps): TypeScript @types packages are convention-loaded; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/leaflet.markercluster | AI (phantom-deps): TypeScript @types packages are convention-loaded; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.1.24 | 20 / 18 | |
| 5.1.23 | 20 / 18 | |
| 5.1.22 | 20 / 18 | |
| 5.1.20 | 20 / 18 | |
| 5.1.19 | 20 / 18 | |
| 5.1.18 | 20 / 18 | |
| 5.1.16 | 20 / 18 | |
| 5.1.15 | 20 / 18 | |
| 5.1.14 | 20 / 18 | |
| 5.1.13 | 20 / 18 | |
| 5.1.12 | 20 / 18 | |
| 5.1.11 | 20 / 18 | |
| 5.1.10 | 20 / 18 | |
| 5.1.9 | 20 / 18 |
v5.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.