@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 — 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/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 |
v4.4.2
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.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.