@shapediver/viewer.rendering-engine.rendering-engine-threejs
This package is part of the [`@shapediver/viewer`](https://www.npmjs.com/package/@shapediver/viewer), you can find all information [here](https://viewer.shapediver.com/v3/latest/api/index.html).
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/three/font.js | AI (source-diff): File contains Three.js FontLoader glyph path data (JSON font definition), not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/managers/postprocessing/ao/hbao/shader/hbao_utils.d.ts | AI (source-diff): File contains readable GLSL shader source as a TypeScript string constant; long lines are shader code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@tweenjs/tween.js | AI (phantom-deps): Referenced in config; loaded by convention in this monorepo. | ai | |
| phantom-deps | phantom-dep:@shapediver/viewer.data-engine.shared-types | AI (phantom-deps): Same-org monorepo dependency; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/three | AI (phantom-deps): Framework-scoped types loaded by convention in Three.js projects; stable pattern. | ai | |
| phantom-deps | phantom-dep:@shapediver/viewer.data-engine.gltf-converter | AI (phantom-deps): Same-org monorepo dependency; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@shapediver/viewer.data-engine.tag3d-engine | AI (phantom-deps): Same-org monorepo dependency; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/stats.js | AI (phantom-deps): Framework-scoped types loaded by convention; stable pattern. | ai |
Versions (showing 51 of 97)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 22 / 0 | |
| 3.16.10 | 22 / 0 | |
| 3.16.9 | 22 / 0 | |
| 3.16.8 | 22 / 0 | |
| 3.16.7 | 22 / 0 | |
| 3.16.6 | 22 / 0 | |
| 3.16.5 | 22 / 0 | |
| 3.16.4 | 22 / 0 | |
| 3.16.3 | 22 / 0 | |
| 3.16.2 | 22 / 0 | |
| 3.16.1 | 22 / 0 | |
| 3.16.0 | 22 / 0 | |
| 3.15.12 | 22 / 0 | |
| 3.15.11 | 22 / 0 | |
| 3.15.10 | 22 / 0 | |
| 3.15.9 | 22 / 0 | |
| 3.15.8 | 22 / 0 | |
| 3.15.7 | 22 / 0 | |
| 3.15.6 | 22 / 0 | |
| 3.15.5 | 22 / 0 | |
| 3.15.4 | 22 / 0 | |
| 3.15.3 | 22 / 0 | |
| 3.15.2 | 22 / 0 | |
| 3.15.1 | 22 / 0 | |
| 3.15.0 | 22 / 0 | |
| 3.14.10 | 22 / 0 | |
| 3.14.9 | 22 / 0 | |
| 3.14.8 | 22 / 0 | |
| 3.14.7 | 22 / 0 | |
| 3.14.6 | 22 / 0 | |
| 3.14.5 | 22 / 0 | |
| 3.14.4 | 22 / 0 | |
| 3.14.3 | 22 / 0 | |
| 3.14.2 | 22 / 0 | |
| 3.14.1 | 22 / 0 | |
| 3.14.0 | 22 / 0 | |
| 3.13.20 | 22 / 0 | |
| 3.13.19 | 22 / 0 | |
| 3.13.18 | 22 / 0 | |
| 3.13.17 | 22 / 0 | |
| 3.13.16 | 22 / 0 | |
| 3.13.15 | 22 / 0 | |
| 3.13.14 | 22 / 0 | |
| 3.13.13 | 22 / 0 | |
| 3.13.12 | 22 / 0 | |
| 3.13.11 | 22 / 0 | |
| 3.13.10 | 22 / 0 | |
| 3.13.9 | 22 / 0 | |
| 3.13.8 | 22 / 0 | |
| 3.13.7 | 22 / 0 | |
| 3.13.6 | 22 / 0 |
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.