deck.gl
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/dist.dev.js | AI (source-diff): Long encoded string is the meshopt WebAssembly decoder (wasm_base), a documented artifact in loaders.gl/gltf bundled output. | ai | |
| source-diff | encoded-string-file:dist.min.js | AI (source-diff): Long encoded string is bundled GLSL shader source and WebGL code, standard in deck.gl minified bundle. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): deck.gl is an actively maintained vis.gl project with 722 versions; dormancy signal is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@deck.gl/arcgis | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@deck.gl/mapbox | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@luma.gl/engine | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@deck.gl/json | AI (phantom-deps): Umbrella re-export package; sub-packages listed as deps but not directly imported in bundle entry. | ai | |
| phantom-deps | phantom-dep:@deck.gl/extensions | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@deck.gl/google-maps | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@loaders.gl/core | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@luma.gl/core | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@deck.gl/carto | AI (phantom-deps): Umbrella re-export package; stable false positive for this monorepo pattern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 9.3.2 | 16 / 0 | |
| 9.3.1 | 16 / 0 | |
| 9.3.0 | 16 / 0 | |
| 9.2.11 | 16 / 0 | |
| 9.2.10 | 16 / 0 | |
| 9.2.9 | 16 / 0 | |
| 9.2.8 | 16 / 0 | |
| 9.2.7 | 16 / 0 | |
| 9.1.15 | 16 / 0 | |
| 9.1.14 | 16 / 0 | |
| 9.1.13 | 16 / 0 | |
| 9.1.12 | 16 / 0 |
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
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.11
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.10
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.9
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.15
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.13
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.