@pandacss/parser
The static parser for panda css
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; expected for chakra-ui/panda monorepo. | ai | |
| typosquat | typosquat.levenshtein:parcel | AI (typosquat): @pandacss/parser is a scoped package in the official PandaCSS namespace (chakra-ui/panda monorepo). The Levenshtein match against 'parcel' is a structural false positive — not a typosquat. | ai | |
| dependencies | unvetted-dep:@pandacss/core | AI (dependencies): First-party dependency within the same @pandacss scoped monorepo; always expected for this package. | ai | |
| dependencies | unvetted-dep:@pandacss/config | AI (dependencies): First-party dependency within the same @pandacss scoped monorepo; always expected for this package. | ai | |
| dependencies | unvetted-dep:@pandacss/extractor | AI (dependencies): First-party dependency within the same @pandacss scoped monorepo; always expected for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.11.3 | 8 / 3 | |
| 1.11.2 | 8 / 3 | |
| 1.11.1 | 8 / 3 | |
| 1.11.0 | 8 / 3 | |
| 1.10.0 | 8 / 3 | |
| 1.9.1 | 10 / 2 | |
| 1.9.0 | 10 / 2 | |
| 1.8.2 | 10 / 2 | |
| 1.8.1 | 10 / 2 | |
| 1.8.0 | 10 / 2 | |
| 1.7.3 | 10 / 2 | |
| 1.7.2 | 10 / 2 | |
| 1.7.1 | 10 / 2 | |
| 1.7.0 | 10 / 2 | |
| 1.6.1 | 10 / 2 | |
| 1.6.0 | 10 / 2 | |
| 1.5.1 | 10 / 2 | |
| 1.5.0 | 10 / 2 | |
| 1.4.3 | 10 / 2 | |
| 1.4.2 | 10 / 2 | |
| 1.4.1 | 10 / 2 | |
| 1.4.0 | 10 / 2 | |
| 1.3.1 | 10 / 2 | |
| 1.3.0 | 10 / 2 | |
| 1.2.0 | 10 / 2 | |
| 1.1.0 | 10 / 2 | |
| 1.0.1 | 10 / 2 | |
| 1.0.0 | 10 / 2 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.