@luma.gl/gltf
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped package @luma.gl/gltf is not a typosquat of glob; Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @luma.gl/gltf is not a typosquat of got; Levenshtein match is a false positive. | ai | |
| phantom-deps | phantom-dep:@loaders.gl/core | AI (phantom-deps): @loaders.gl/core is a declared dependency used in config/build files; stable false positive for this package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 9.3.6 | 4 / 0 | |
| 9.3.5 | 4 / 0 | |
| 9.3.4 | 4 / 0 | |
| 9.3.3 | 4 / 0 | |
| 9.3.2 | 4 / 0 | |
| 9.3.1 | 4 / 0 | |
| 9.3.0 | 4 / 0 | |
| 9.2.6 | 4 / 0 | |
| 9.2.5 | 4 / 0 | |
| 9.2.4 | 4 / 0 | |
| 9.2.3 | 4 / 0 | |
| 9.2.2 | 4 / 0 | |
| 9.2.1 | 4 / 0 | |
| 9.2.0 | 4 / 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 | 3 / 0 | |
| 9.0.27 | 3 / 0 | |
| 9.0.26 | 3 / 0 | |
| 9.0.25 | 3 / 0 | |
| 9.0.24 | 3 / 0 | |
| 9.0.23 | 3 / 0 | |
| 9.0.21 | 3 / 0 | |
| 9.0.20 | 3 / 0 | |
| 9.0.19 | 3 / 0 | |
| 9.0.17 | 3 / 0 | |
| 9.0.16 | 3 / 0 | |
| 9.0.15 | 3 / 0 | |
| 9.0.14 | 3 / 0 | |
| 9.0.12 | 3 / 0 |
v9.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pessimistress) than the most recent previously approved version (felixpalmer) on 2024-05-10, but pessimistress is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.