@luma.gl/webgl
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established luma.gl package; lack of provenance is consistent across all prior versions. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 9.3.6 | 2 / 0 | |
| 9.3.5 | 2 / 0 | |
| 9.3.4 | 2 / 0 | |
| 9.3.3 | 2 / 0 | |
| 9.3.2 | 2 / 0 | |
| 9.3.1 | 2 / 0 | |
| 9.3.0 | 2 / 0 | |
| 9.2.6 | 3 / 0 | |
| 9.2.5 | 3 / 0 | |
| 9.2.4 | 3 / 0 | |
| 9.2.3 | 3 / 0 | |
| 9.2.2 | 3 / 0 | |
| 9.2.1 | 3 / 0 | |
| 9.2.0 | 3 / 0 | |
| 9.1.10 | 3 / 0 | |
| 9.1.9 | 3 / 0 | |
| 9.1.7 | 3 / 0 | |
| 9.1.6 | 3 / 0 | |
| 9.1.5 | 3 / 0 | |
| 9.1.4 | 3 / 0 | |
| 9.1.3 | 3 / 0 | |
| 9.1.2 | 3 / 0 | |
| 9.1.1 | 3 / 0 | |
| 9.1.0 | 3 / 0 | |
| 9.0.28 | 2 / 0 | |
| 9.0.27 | 2 / 0 | |
| 9.0.26 | 2 / 0 | |
| 9.0.25 | 2 / 0 | |
| 9.0.24 | 2 / 0 | |
| 9.0.23 | 2 / 0 | |
| 9.0.21 | 2 / 0 | |
| 9.0.20 | 2 / 0 | |
| 9.0.19 | 2 / 0 | |
| 9.0.17 | 2 / 0 | |
| 9.0.16 | 2 / 0 | |
| 9.0.15 | 2 / 0 | |
| 9.0.14 | 2 / 0 | |
| 9.0.12 | 2 / 0 |
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.