@shapediver/sdk.platform-api-sdk-v1
SDK to communicate with the Platform API version 1
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established ShapeDiver org package; lack of provenance is consistent across all their releases. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 2.29.19 | 4 / 7 | |
| 2.29.18 | 4 / 7 | |
| 2.29.17 | 4 / 7 | |
| 2.29.16 | 4 / 6 | |
| 2.29.15 | 4 / 6 | |
| 2.29.14 | 4 / 6 | |
| 2.29.13 | 4 / 6 | |
| 2.29.12 | 4 / 6 | |
| 2.29.11 | 4 / 6 | |
| 2.29.10 | 4 / 6 | |
| 2.29.9 | 4 / 6 | |
| 2.29.8 | 4 / 6 | |
| 2.29.7 | 4 / 6 | |
| 2.29.1 | 4 / 6 | |
| 2.29.0 | 4 / 6 | |
| 2.28.9 | 4 / 6 | |
| 2.28.8 | 4 / 6 | |
| 2.28.7 | 4 / 6 | |
| 2.28.6 | 4 / 6 | |
| 2.28.5 | 4 / 6 | |
| 2.28.4 | 4 / 6 | |
| 2.28.3 | 4 / 6 | |
| 2.28.2 | 4 / 6 | |
| 2.28.1 | 4 / 6 | |
| 2.27.11 | 4 / 6 | |
| 2.27.10 | 4 / 6 | |
| 2.27.9 | 4 / 6 | |
| 2.27.8 | 4 / 6 | |
| 2.27.7 | 4 / 6 | |
| 2.27.6 | 4 / 6 | |
| 2.27.5 | 4 / 6 | |
| 2.27.4 | 4 / 6 | |
| 2.27.3 | 4 / 6 | |
| 2.27.2 | 4 / 6 | |
| 2.27.1 | 4 / 6 | |
| 2.27.0 | 4 / 6 | |
| 2.26.1 | 4 / 6 | |
| 2.26.0 | 4 / 6 | |
| 2.25.0 | 4 / 6 | |
| 2.24.0 | 4 / 6 | |
| 2.23.1 | 4 / 6 |
v2.29.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matt_at_shapediver) than the most recent previously approved version (dmitry_at_shapediver) on 2024-07-24, but matt_at_shapediver is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.26.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dmitry_at_shapediver) than the most recent previously approved version (matt_at_shapediver) on 2024-06-19, but dmitry_at_shapediver is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.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.