react-sizeme
Make your React Components aware of their width and/or height!
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:umd/react-sizeme.js | AI (source-diff): Standard Webpack UMD bundle output; 'network + exec' pattern is Webpack module loader boilerplate, not malicious code. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; long-established publisher with strong track record. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 4 / 44 | |
| 3.0.1 | 4 / 44 | |
| 3.0.0 | 4 / 44 | |
| 2.6.12 | 4 / 44 | |
| 2.6.11 | 5 / 44 | |
| 2.6.10 | 4 / 47 | |
| 2.6.9 | 4 / 47 | |
| 2.6.8 | 4 / 46 | |
| 2.6.7 | 4 / 46 | |
| 2.6.6 | 5 / 46 | |
| 2.6.5 | 5 / 46 | |
| 2.6.4 | 5 / 46 | |
| 2.6.3 | 5 / 46 | |
| 2.6.2 | 5 / 46 | |
| 2.6.1 | 5 / 46 | |
| 2.6.0 | 5 / 46 | |
| 2.5.2 | 5 / 42 | |
| 2.5.1 | 5 / 42 | |
| 2.4.4 | 4 / 41 | |
| 2.4.3 | 4 / 41 | |
| 2.4.2 | 4 / 41 | |
| 2.4.1 | 4 / 41 | |
| 2.4.0 | 4 / 41 | |
| 2.3.6 | 3 / 44 | |
| 2.3.5 | 3 / 44 | |
| 2.3.4 | 3 / 46 | |
| 2.3.3 | 3 / 46 | |
| 2.3.2 | 3 / 46 | |
| 2.3.1 | 3 / 44 | |
| 2.3.0 | 3 / 44 | |
| 2.2.0 | 3 / 40 | |
| 2.1.4 | 3 / 40 | |
| 2.1.3 | 3 / 40 | |
| 2.1.2 | 3 / 40 | |
| 2.1.1 | 3 / 40 | |
| 2.1.0 | 3 / 40 | |
| 2.0.3 | 3 / 40 | |
| 2.0.2 | 3 / 40 | |
| 2.0.1 | 3 / 38 | |
| 2.0.0 | 3 / 38 | |
| 1.0.6 | 3 / 38 | |
| 1.0.5 | 3 / 38 | |
| 1.0.4 | 2 / 39 | |
| 1.0.3 | 2 / 39 | |
| 1.0.2 | 2 / 39 | |
| 1.0.1 | 2 / 39 | |
| 1.0.0 | 2 / 39 | |
| 0.0.6 | 0 / 36 | |
| 0.0.5 | 0 / 36 | |
| 0.0.4 | 0 / 36 | |
| 0.0.3 | 0 / 36 | |
| 0.0.2 | 0 / 36 | |
| 0.0.1 | 0 / 36 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.