react-resize-detector
React resize detector
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 changed back to maslianok, the original author/repo owner. snelsi is a listed contributor who was publishing on their behalf. This is a legitimate maintainer resumption. | ai |
Versions (showing 51 of 109)
| Version | Deps | Published |
|---|---|---|
| 12.3.0 | 1 / 15 | |
| 12.2.0 | 1 / 16 | |
| 12.1.0 | 1 / 16 | |
| 12.0.2 | 1 / 15 | |
| 12.0.1 | 1 / 16 | |
| 12.0.0 | 1 / 16 | |
| 11.0.1 | 1 / 15 | |
| 10.0.1 | 1 / 17 | |
| 10.0.0 | 1 / 17 | |
| 9.1.1 | 1 / 17 | |
| 9.1.0 | 1 / 16 | |
| 9.0.0 | 1 / 16 | |
| 8.1.0 | 1 / 16 | |
| 8.0.5 | 1 / 16 | |
| 8.0.4 | 1 / 16 | |
| 8.0.3 | 1 / 16 | |
| 8.0.2 | 1 / 16 | |
| 8.0.1 | 1 / 16 | |
| 8.0.0 | 1 / 16 | |
| 7.1.2 | 1 / 24 | |
| 7.1.1 | 1 / 24 | |
| 7.1.0 | 2 / 23 | |
| 7.0.2 | 2 / 23 | |
| 7.0.1 | 2 / 23 | |
| 7.0.0 | 2 / 23 | |
| 6.7.8 | 3 / 23 | |
| 6.7.7 | 4 / 23 | |
| 6.7.6 | 4 / 23 | |
| 6.7.5 | 4 / 23 | |
| 6.7.4 | 4 / 23 | |
| 6.7.3 | 4 / 23 | |
| 6.7.2 | 4 / 23 | |
| 6.7.1 | 4 / 23 | |
| 6.7.0 | 4 / 23 | |
| 6.6.5 | 4 / 23 | |
| 6.6.4 | 4 / 23 | |
| 6.6.3 | 4 / 23 | |
| 6.6.2 | 4 / 23 | |
| 6.6.1 | 4 / 23 | |
| 6.6.0 | 4 / 22 | |
| 6.5.0 | 4 / 22 | |
| 6.3.3 | 4 / 22 | |
| 6.3.2 | 4 / 22 | |
| 6.3.1 | 4 / 22 | |
| 6.3.0 | 4 / 22 | |
| 6.2.1 | 4 / 22 | |
| 6.2.0 | 4 / 22 | |
| 6.1.0 | 5 / 23 | |
| 5.2.0 | 4 / 18 | |
| 5.1.3 | 5 / 18 | |
| 5.1.2 | 5 / 18 |
v12.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-08-27. 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.
v12.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-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.
v12.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
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: maslianok.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.