@deck.gl-community/editable-layers
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:uuid | AI (phantom-deps): uuid is a transitive dependency; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): eventemitter3 is a transitive dependency; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Framework-scoped type package, loaded by convention; stable pattern for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.3.5 | 39 / 0 | |
| 9.3.2 | 39 / 0 | |
| 9.3.1 | 39 / 0 | |
| 9.2.8 | 41 / 0 | |
| 9.2.5 | 41 / 0 | |
| 9.1.1 | 36 / 0 |
v9.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.