@shapediver/viewer.api.general
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 |
|---|---|---|---|---|
| license | uncommon-license:polyform-noncommercial-1.0.0 | AI (license): Intentional non-commercial license; stable for this package's ecosystem context. | ai | |
| npm-metadata | no-description | AI (npm-metadata): ShapeDiver internal API package; sparse metadata is consistent across their entire package family. | ai | |
| dependencies | unvetted-dep:@shapediver/viewer.data-engine.geometry-engine | AI (dependencies): Sibling package from same ShapeDiver org/monorepo; versioned in lockstep, not a third-party risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large monorepo SDK; sparse README/metadata is consistent across all 165 versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire ShapeDiver Viewer package family; not a per-version anomaly. | ai | |
| phantom-deps | phantom-dep:gl-matrix | AI (phantom-deps): gl-matrix is a declared dependency; likely re-exported or used in type definitions rather than directly imported. | ai |
Versions (showing 51 of 97)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 5 / 0 | |
| 3.16.10 | 5 / 0 | |
| 3.16.9 | 5 / 0 | |
| 3.16.8 | 5 / 0 | |
| 3.16.7 | 5 / 0 | |
| 3.16.6 | 5 / 0 | |
| 3.16.5 | 5 / 0 | |
| 3.16.4 | 5 / 0 | |
| 3.16.3 | 5 / 0 | |
| 3.16.2 | 5 / 0 | |
| 3.16.1 | 5 / 0 | |
| 3.16.0 | 5 / 0 | |
| 3.15.12 | 5 / 0 | |
| 3.15.11 | 5 / 0 | |
| 3.15.10 | 5 / 0 | |
| 3.15.9 | 5 / 0 | |
| 3.15.8 | 5 / 0 | |
| 3.15.7 | 5 / 0 | |
| 3.15.6 | 5 / 0 | |
| 3.15.5 | 5 / 0 | |
| 3.15.4 | 5 / 0 | |
| 3.15.3 | 5 / 0 | |
| 3.15.2 | 5 / 0 | |
| 3.15.1 | 5 / 0 | |
| 3.15.0 | 5 / 0 | |
| 3.14.10 | 5 / 0 | |
| 3.14.9 | 5 / 0 | |
| 3.14.8 | 5 / 0 | |
| 3.14.7 | 5 / 0 | |
| 3.14.6 | 5 / 0 | |
| 3.14.5 | 5 / 0 | |
| 3.14.4 | 5 / 0 | |
| 3.14.3 | 5 / 0 | |
| 3.14.2 | 5 / 0 | |
| 3.14.1 | 5 / 0 | |
| 3.14.0 | 5 / 0 | |
| 3.13.20 | 5 / 0 | |
| 3.13.19 | 5 / 0 | |
| 3.13.18 | 5 / 0 | |
| 3.13.17 | 5 / 0 | |
| 3.13.16 | 5 / 0 | |
| 3.13.15 | 5 / 0 | |
| 3.13.14 | 5 / 0 | |
| 3.13.13 | 5 / 0 | |
| 3.13.12 | 5 / 0 | |
| 3.13.11 | 5 / 0 | |
| 3.13.10 | 5 / 0 | |
| 3.13.9 | 5 / 0 | |
| 3.13.8 | 5 / 0 | |
| 3.13.7 | 5 / 0 | |
| 3.13.6 | 5 / 0 |
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.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.
v3.15.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.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.
v3.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.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.
v3.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.