@needle-tools/gltf-build-pipeline
Pipeline and tools for optimizing gltf files using gltf-transform and compression settings within glTF extensions
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:tools/pmrem/basis/wasm/basis_encoder_threads.js | AI (source-diff): Emscripten-bundled wasm glue for Basis encoder, not obfuscation. | ai | |
| source-diff | net-exec-file:tools/pmrem/basis/wasm/basis_encoder_threads.js | AI (source-diff): fetch() only loads companion .wasm binary; standard Emscripten pattern. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): basisu is the known Google Basis Universal compressor CLI, matches package purpose. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Part of Emscripten runtime glue, not arbitrary eval. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): glob is a declared dep used transitively/in config; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Technical glTF pipeline tool; link-heavy README is documentation, not a phishing farm. | ai | |
| phantom-deps | phantom-dep:ndarray | AI (phantom-deps): ndarray declared dep used via config/indirect; stable false positive. | ai | |
| phantom-deps | phantom-dep:ndarray-pixels | AI (phantom-deps): ndarray-pixels declared dep used via config/indirect; stable false positive. | ai | |
| phantom-deps | phantom-dep:ndarray-lanczos | AI (phantom-deps): ndarray-lanczos declared dep used via config/indirect; stable false positive. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 20 / 7 | |
| 2.15.12 | 19 / 6 | |
| 2.14.1 | 19 / 3 | |
| 2.14.0 | 19 / 3 | |
| 2.13.1 | 19 / 3 | |
| 2.13.0 | 19 / 3 | |
| 2.12.1 | 18 / 3 | |
| 2.12.0 | 18 / 3 | |
| 2.11.4 | 18 / 3 | |
| 2.11.3 | 18 / 3 | |
| 2.11.2 | 18 / 3 | |
| 2.11.1 | 18 / 3 | |
| 2.11.0 | 18 / 3 | |
| 2.10.2 | 18 / 3 | |
| 2.10.1 | 18 / 3 | |
| 2.10.0 | 18 / 3 | |
| 2.9.5 | 18 / 3 | |
| 2.9.4 | 18 / 3 | |
| 2.9.3 | 18 / 3 | |
| 2.9.2 | 18 / 3 | |
| 2.9.1 | 18 / 3 | |
| 2.9.0 | 18 / 3 | |
| 2.8.1 | 18 / 3 | |
| 2.7.1 | 18 / 3 | |
| 2.7.0 | 18 / 3 | |
| 2.5.0 | 18 / 3 | |
| 2.4.0 | 18 / 3 |
v3.0.0
4 findingsPackage contains compiled binaries that could be backdoors: • tools/pmrem/basis/linux/basisu • tools/pmrem/basis/osx/basisu • tools/pmrem/basis/win/basisu.exe
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.