@stylexjs/stylex
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 | publisher-changed | AI (provenance): necolas is a long-standing, highly trusted Meta/Facebook publisher; transition from mellyeliu is consistent with org maintainer rotation. | ai | |
| phantom-deps | phantom-dep:styleq | AI (phantom-deps): Declared dependency; used indirectly in build pipeline. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): Declared dependency; used indirectly in build pipeline. | ai | |
| phantom-deps | phantom-dep:css-mediaquery | AI (phantom-deps): Declared dependency; used indirectly in build pipeline. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.18.3 | 3 / 19 | |
| 0.18.2 | 3 / 19 | |
| 0.18.1 | 3 / 19 | |
| 0.18.0 | 3 / 19 | |
| 0.17.5 | 3 / 19 | |
| 0.17.4 | 3 / 20 | |
| 0.17.3 | 3 / 20 | |
| 0.17.2 | 3 / 20 | |
| 0.17.1 | 3 / 20 | |
| 0.17.0 | 3 / 20 | |
| 0.16.3 | 3 / 20 | |
| 0.16.2 | 3 / 20 | |
| 0.16.1 | 3 / 20 | |
| 0.16.0 | 3 / 20 | |
| 0.15.4 | 3 / 20 | |
| 0.15.3 | 3 / 20 | |
| 0.15.2 | 3 / 20 | |
| 0.15.1 | 3 / 20 | |
| 0.15.0 | 3 / 20 | |
| 0.14.3 | 3 / 20 | |
| 0.14.2 | 3 / 20 | |
| 0.14.1 | 3 / 20 | |
| 0.14.0 | 3 / 20 | |
| 0.13.1 | 3 / 20 | |
| 0.13.0 | 3 / 20 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
2 findingsThis version was published by a different npm account than previous versions on 2025-07-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
2 findingsThis version was published by a different npm account than previous versions on 2025-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
2 findingsThis version was published by a different npm account than previous versions on 2025-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.