@commercetools-demo/puck-api
API client and React hooks for the Puck CMS integration
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm packages); no other risk signals present. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 1 / 3 | |
| 0.8.0 | 1 / 3 | |
| 0.7.1 | 1 / 3 | |
| 0.7.0 | 1 / 3 | |
| 0.6.1 | 1 / 3 | |
| 0.6.0 | 1 / 3 | |
| 0.5.2 | 1 / 3 | |
| 0.5.1 | 1 / 3 | |
| 0.5.0 | 1 / 3 | |
| 0.4.0 | 1 / 3 | |
| 0.3.0 | 1 / 3 | |
| 0.2.1 | 1 / 3 | |
| 0.2.0 | 1 / 3 | |
| 0.1.0 | 1 / 3 |
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.