← Home

@commercetools-demo/puck-content-manager

UI components for managing standalone Puck content items

15
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

lgiavedonibehnam777

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@commercetools-uikit/tag AI (phantom-deps): Declared as runtime dep and referenced in config; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@commercetools-uikit/design-system AI (phantom-deps): Design system package referenced in config files only; stable false positive for this UI component package. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. ai

Versions (showing 15 of 15)

Version Deps Published
0.8.1 6 / 5
0.8.0 6 / 5
0.7.1 6 / 5
0.7.0 6 / 5
0.6.1 6 / 5
0.6.0 6 / 5
0.5.2 19 / 5
0.5.1 19 / 5
0.5.0 19 / 5
0.4.0 19 / 5
0.3.1 19 / 5
0.3.0 19 / 5
0.2.1 16 / 5
0.2.0 16 / 5
0.1.0 16 / 4

v0.8.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.