@deck.gl/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @deck.gl/core is a scoped package in the visgl ecosystem; Levenshtein match to 'cors' is a false positive. | ai | |
| phantom-deps | phantom-dep:gl-matrix | AI (phantom-deps): gl-matrix is a legitimate runtime dep used transitively; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:@probe.gl/env | AI (phantom-deps): First-party visgl dep; phantom-dep heuristic fires on config references, not a real concern. | ai | |
| phantom-deps | phantom-dep:@types/offscreencanvas | AI (phantom-deps): Type-only package loaded by convention; phantom-dep finding is expected and benign. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.3.3 | 16 / 0 | |
| 9.3.2 | 16 / 0 | |
| 9.3.1 | 16 / 0 | |
| 9.3.0 | 16 / 0 | |
| 9.1.13 | 17 / 0 | |
| 9.1.12 | 17 / 0 |
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
2 findingsPackage name '@deck.gl/core' is 1 edit(s) away from popular package 'cors'.
Package 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.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.