react-freeze
React Freeze
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): Publisher change from kmag to kacperkapusciak reflects a legitimate Software Mansion team handoff; kacperkapusciak is a well-established publisher with 1354 approved packages and no rejections. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer kacperkapusciak is a trusted, long-standing npm publisher consistent with the software-mansion org that owns the repository. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; absence is expected for this package's age and ecosystem context. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 0 / 25 | |
| 1.0.3 | 0 / 25 | |
| 1.0.2 | 0 / 25 | |
| 1.0.1 | 0 / 26 | |
| 1.0.0 | 0 / 26 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-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.
v1.0.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.