@shapediver/sdk.sdtf-v1
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@shapediver/sdk.sdtf-core | AI (dependencies): Sibling monorepo package from same org; version-locked to match this release. | ai | |
| dependencies | unvetted-dep:@shapediver/sdk.sdtf-geometry | AI (dependencies): Sibling monorepo package from same org; version-locked to match this release. | ai | |
| dependencies | unvetted-dep:@shapediver/sdk.sdtf-primitives | AI (dependencies): Sibling monorepo package from same org; version-locked to match this release. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.7.4 | 5 / 7 | |
| 1.7.3 | 5 / 7 | |
| 1.7.2 | 5 / 7 | |
| 1.7.1 | 5 / 7 | |
| 1.7.0 | 5 / 7 | |
| 1.6.2 | 5 / 7 | |
| 1.6.1 | 5 / 7 | |
| 1.6.0 | 5 / 7 | |
| 1.5.3 | 5 / 7 | |
| 1.5.2 | 5 / 7 | |
| 1.5.1 | 5 / 7 | |
| 1.5.0 | 5 / 7 | |
| 1.4.2 | 5 / 7 | |
| 1.4.1 | 5 / 7 | |
| 1.4.0 | 5 / 7 | |
| 1.3.1 | 5 / 7 | |
| 1.3.0 | 5 / 6 | |
| 1.2.0 | 5 / 6 | |
| 1.1.3 | 5 / 6 | |
| 1.1.2 | 5 / 6 | |
| 1.1.1 | 5 / 6 | |
| 1.1.0 | 5 / 6 | |
| 1.0.0 | 5 / 6 |
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.