← Home

@pandacss/config

Find and load panda config

30
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

segunadebayo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA provenance; stable for this package. ai
dependencies unvetted-dep:merge-anything AI (dependencies): merge-anything is a legitimate, well-known deep-merge utility; its use in a CSS config package is expected and benign. Stable across versions. ai
provenance no-provenance AI (provenance): Established package from trusted publisher (segunadebayo/chakra-ui); lack of provenance is common and not a risk signal here. ai

Versions (showing 30 of 30)

Version Deps Published
1.11.5 10 / 1
1.11.4 9 / 1
1.11.3 9 / 1
1.11.2 9 / 1
1.11.1 9 / 1
1.11.0 9 / 1
1.10.0 9 / 1
1.9.1 9 / 1
1.9.0 9 / 1
1.8.2 9 / 1
1.8.1 9 / 1
1.8.0 9 / 1
1.7.3 9 / 1
1.7.2 9 / 1
1.7.1 9 / 1
1.7.0 10 / 1
1.6.1 10 / 1
1.6.0 10 / 1
1.5.1 10 / 1
1.5.0 10 / 1
1.4.3 10 / 1
1.4.2 10 / 1
1.4.1 10 / 1
1.4.0 10 / 1
1.3.1 10 / 1
1.3.0 10 / 1
1.2.0 10 / 1
1.1.0 10 / 1
1.0.1 10 / 1
1.0.0 10 / 1

v1.11.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.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.

v1.4.3

1 finding
INFO No provenance attestation provenance

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

v1.4.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.

v1.4.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.

v1.4.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.

v1.3.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.

v1.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.