@stylexjs/babel-plugin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Meta/Facebook package; provenance absence is consistent across all prior versions. | ai | |
| dependencies | unvetted-dep:@stylexjs/stylex | AI (dependencies): Same-monorepo sibling dep from facebook/stylex; version-locked to match this package, stable pattern across releases. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 8 / 10 | |
| 0.18.3 | 8 / 10 | |
| 0.18.2 | 8 / 10 | |
| 0.18.1 | 8 / 10 | |
| 0.17.1 | 8 / 9 | |
| 0.17.0 | 8 / 9 | |
| 0.15.2 | 7 / 9 | |
| 0.14.2 | 7 / 9 | |
| 0.14.1 | 7 / 9 | |
| 0.14.0 | 7 / 9 | |
| 0.13.1 | 7 / 9 | |
| 0.13.0 | 7 / 9 |
v0.19.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mellyeliu) than the most recent previously approved version (naman34) on 2026-06-16, but mellyeliu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.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.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.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.