@loaders.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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/dist.dev.js | AI (source-diff): Long string is the embedded meshopt WASM decoder in bundled output; stable across versions. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Long string is a WebAssembly base64 blob for meshopt decoder — expected artifact in this glTF loader. | ai | |
| source-diff | encoded-string-file:dist/dist.min.js | AI (source-diff): Minified bundle output from documented build-bundle script; not obfuscation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 358 versions over 2700 days; dormancy signal is a false positive for this active monorepo package. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped package in the visgl/loaders.gl monorepo; Levenshtein match to 'glob' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package in the visgl/loaders.gl monorepo; Levenshtein match to 'got' is a false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 6 / 0 | |
| 4.4.2 | 6 / 0 | |
| 4.4.1 | 6 / 0 | |
| 4.4.0 | 6 / 0 | |
| 4.3.4 | 6 / 0 | |
| 4.3.3 | 6 / 0 | |
| 4.3.2 | 6 / 0 | |
| 4.3.1 | 6 / 0 | |
| 4.3.0 | 6 / 0 | |
| 4.2.5 | 6 / 0 | |
| 4.2.4 | 6 / 0 | |
| 4.2.3 | 6 / 0 | |
| 4.2.2 | 6 / 0 |
v4.3.3
2 findingsModified 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.
v4.3.2
2 findingsModified 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.
v4.3.1
2 findingsModified 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.
v4.3.0
2 findingsModified 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.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
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 (belom88) than the most recent previously approved version (dterekhova) on 2024-09-20, but belom88 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.
v4.2.3
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 (dterekhova) than the most recent previously approved version (belom88) on 2024-09-03, but dterekhova 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.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.