@pandacss/reporter
Track and report usage of tokens and recipes
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA provenance; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established PandaCSS monorepo package from a highly trusted publisher; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.11.3 | 7 / 1 | |
| 1.11.2 | 7 / 1 | |
| 1.11.1 | 7 / 1 | |
| 1.11.0 | 7 / 1 | |
| 1.10.0 | 7 / 1 | |
| 1.9.1 | 7 / 1 | |
| 1.9.0 | 7 / 1 | |
| 1.8.2 | 7 / 1 | |
| 1.8.1 | 7 / 1 | |
| 1.8.0 | 7 / 1 | |
| 1.7.3 | 7 / 1 | |
| 1.7.2 | 7 / 1 | |
| 1.7.1 | 7 / 1 | |
| 1.7.0 | 7 / 1 | |
| 1.6.1 | 7 / 1 | |
| 1.6.0 | 7 / 1 | |
| 1.5.1 | 7 / 1 | |
| 1.5.0 | 7 / 1 | |
| 1.4.3 | 7 / 1 | |
| 1.4.2 | 7 / 1 | |
| 1.4.1 | 7 / 1 | |
| 1.4.0 | 7 / 1 | |
| 1.3.1 | 7 / 1 | |
| 1.3.0 | 7 / 1 | |
| 1.2.0 | 7 / 1 | |
| 1.1.0 | 7 / 1 | |
| 1.0.1 | 7 / 1 | |
| 1.0.0 | 7 / 1 |
v1.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.2
2 findingsThis version was published by a different npm account than previous versions on 2026-06-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.