@luma.gl/shadertools
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:dist/modules/lighting/phong-material/phong-shaders-wgsl.d.ts | AI (source-diff): WGSL shader source string in .d.ts export; benign. | ai | |
| source-diff | obfuscated-file:dist/modules/math/fp64/fp64-functions-glsl.d.ts | AI (source-diff): Long-line shader source string in .d.ts export; benign. | ai | |
| source-diff | obfuscated-file:dist/modules/math/fp64/fp64-arithmetic-glsl.d.ts | AI (source-diff): Long-line shader source string in .d.ts export; benign for this shader library. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in WGSL parser codegen, not dynamic eval of untrusted input; stable across versions. | ai | |
| source-diff | obfuscated-file:dist/modules/lighting/pbr-material/pbr-fragment-glsl.d.ts | AI (source-diff): Inlined GLSL shader source as TS string constant; long lines expected, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/modules-webgl1/math/fp64/fp64-arithmetic-glsl.d.ts | AI (source-diff): Inlined GLSL shader source as TS string constant; long lines expected, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/modules-webgl1/math/fp64/fp64-functions-glsl.d.ts | AI (source-diff): Inlined GLSL shader source as TS string constant; long lines expected, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/modules-webgl1/lighting/pbr/pbr-fragment-glsl.d.ts | AI (source-diff): Inlined GLSL shader source as TS string constant; long lines expected, not obfuscation. | ai | |
| dependencies | unvetted-dep:wgsl_reflect | AI (dependencies): wgsl_reflect is a legitimate WGSL reflection library; appropriate dependency for a WebGPU shader tools package. | ai | |
| provenance | no-provenance | AI (provenance): Established luma.gl org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 9.3.6 | 2 / 0 | |
| 9.3.5 | 2 / 0 | |
| 9.3.4 | 2 / 0 | |
| 9.3.3 | 2 / 0 | |
| 9.3.2 | 2 / 0 | |
| 9.3.1 | 2 / 0 | |
| 9.3.0 | 2 / 0 | |
| 9.2.6 | 3 / 0 | |
| 9.2.5 | 3 / 0 | |
| 9.2.4 | 3 / 0 | |
| 9.2.3 | 3 / 0 | |
| 9.2.2 | 3 / 0 | |
| 9.2.1 | 3 / 0 | |
| 9.2.0 | 3 / 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 | 2 / 0 | |
| 9.0.14 | 2 / 0 | |
| 9.0.12 | 2 / 0 |
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.6
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.