← Home

@pyck/panda-preset

26
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

christian-pyck.aimatthias.pyckmmack_pyck

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Likely reflects a build toolchain change (bun-based publish); prepack/postpack scripts confirm intentional workflow shift. ai
npm-metadata no-description AI (npm-metadata): Org-internal preset package; missing description is cosmetic and stable across versions. ai
provenance no-provenance AI (provenance): Published via GitHub Actions; no provenance is common and not a security signal for this package. ai

Versions (showing 26 of 26)

Version Deps Published
0.7.3 1 / 7
0.6.2 1 / 7
0.6.1 1 / 7
0.6.0 1 / 7
0.5.0 1 / 7
0.3.0 1 / 7
0.2.0 1 / 7
0.1.1 1 / 7
0.1.0 1 / 7
0.0.18 1 / 7
0.0.17 0 / 7
0.0.16 0 / 7
0.0.15 0 / 7
0.0.14 0 / 7
0.0.13 0 / 7
0.0.12 0 / 7
0.0.11 0 / 7
0.0.10 0 / 7
0.0.9 0 / 7
0.0.8 0 / 7
0.0.7 0 / 7
0.0.6 0 / 7
0.0.5 0 / 7
0.0.3 0 / 7
0.0.2 0 / 7
0.0.1 0 / 7

v0.6.2

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.

v0.5.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.3.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.2.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.1.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.1.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.0.18

1 finding
INFO No provenance attestation provenance

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