← Home

@pandacss/dev

npm Repository Homepage
27
Versions
—
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; legitimate for this org. ai
phantom-deps phantom-dep:@pandacss/preset-base AI (phantom-deps): Same-org dep likely re-exported or used transitively; stable pattern. ai
phantom-deps phantom-dep:@pandacss/token-dictionary AI (phantom-deps): Same-org dep likely re-exported or used transitively; stable pattern. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): @pandacss/dev is a scoped package in the well-known Panda CSS ecosystem; levenshtein proximity to 'ajv' is coincidental and not a typosquat signal. ai
bogus-package bogus-package AI (bogus-package): @pandacss/dev is the main CLI entry point for Panda CSS, a well-established project with 1008 versions. Short README and missing keywords are cosmetic issues, not spam indicators. ai

Versions (showing 27 of 27)

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

v1.11.2

2 findings
HIGH Publisher changed: segunadebayo → GitHub Actions (on 2026-06-04) provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.9.1

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.2

1 finding
LOW No provenance attestation provenance

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.3

1 finding
LOW No provenance attestation provenance

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

v1.7.2

1 finding
LOW No provenance attestation provenance

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

v1.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.0

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.