@compiled/react
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jackbrown → jackbrownatlassian is an Atlassian corporate account migration; stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jackbrownatlassian is the same Atlassian maintainer under a new corporate npm account. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine Atlassian team roster change; stable for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.21.2 | 1 / 13 | |
| 0.21.1 | 1 / 13 | |
| 0.21.0 | 1 / 10 | |
| 0.20.0 | 1 / 10 | |
| 0.19.1 | 1 / 10 | |
| 0.19.0 | 1 / 10 | |
| 0.18.6 | 1 / 10 | |
| 0.18.5 | 1 / 10 | |
| 0.18.4 | 1 / 10 | |
| 0.18.3 | 1 / 10 | |
| 0.18.2 | 1 / 10 | |
| 0.18.1 | 1 / 10 | |
| 0.18.0 | 1 / 10 | |
| 0.17.3 | 1 / 9 | |
| 0.17.2 | 1 / 9 |
v0.21.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
2 findingsThis version was published by a different npm account than previous versions on 2025-04-16. 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.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.