babylonjs-loaders
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 | obfuscated-file:babylon.glTF2FileLoader.js | AI (source-diff): Standard UMD minified bundle for BabylonJS loader; not obfuscated, just minified distribution artifact. | ai | |
| source-diff | obfuscated-file:babylon.bvhFileLoader.js | AI (source-diff): Standard UMD minified bundle for BabylonJS loader; not obfuscated, just minified distribution artifact. | ai | |
| source-diff | obfuscated-file:babylon.glTF1FileLoader.js | AI (source-diff): Standard UMD minified bundle for BabylonJS loader; not obfuscated, just minified distribution artifact. | ai | |
| source-diff | obfuscated-file:babylon.stlFileLoader.js | AI (source-diff): Standard UMD minified bundle for BabylonJS loader; not obfuscated, just minified distribution artifact. | ai | |
| source-diff | obfuscated-file:babylon.glTFFileLoader.js | AI (source-diff): Standard UMD minified bundle for BabylonJS loader; not obfuscated, just minified distribution artifact. | ai | |
| source-diff | obfuscated-file:babylon.objFileLoader.js | AI (source-diff): Standard UMD minified bundle for BabylonJS loader; not obfuscated, just minified distribution artifact. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in minified bundle output of a well-known 3D engine loader; stable pattern across versions. | ai |
Versions (showing 5 of 105)
| Version | Deps | Published |
|---|---|---|
| 8.37.0 | 2 / 7 | |
| 8.36.1 | 2 / 7 | |
| 8.36.0 | 2 / 7 | |
| 8.35.0 | 2 / 7 | |
| 8.34.1 | 2 / 7 |
v8.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.