react-resizable
A component that is resizable with handles.
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 | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): This is Google's prettify.js syntax highlighter, a well-known minified library bundled in lcov HTML coverage reports. Not malicious — it's a standard coverage report artifact accidentally included in the publish. | ai | |
| provenance | no-provenance | AI (provenance): Established package with strong publisher track record; lack of Sigstore attestation is a process gap, not a security risk for this package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 2 / 35 | |
| 4.0.0 | 2 / 35 | |
| 3.2.0 | 2 / 30 | |
| 3.1.3 | 2 / 29 | |
| 3.1.2 | 2 / 29 | |
| 3.1.1 | 2 / 29 | |
| 3.1.0 | 2 / 29 | |
| 3.0.5 | 2 / 28 | |
| 3.0.4 | 2 / 27 | |
| 3.0.3 | 2 / 27 | |
| 3.0.2 | 2 / 27 | |
| 3.0.1 | 2 / 26 | |
| 3.0.0 | 2 / 26 | |
| 2.0.0 | 2 / 26 | |
| 1.11.1 | 2 / 26 | |
| 1.11.0 | 2 / 26 | |
| 1.10.1 | 2 / 22 | |
| 1.9.0 | 2 / 22 | |
| 1.8.0 | 2 / 20 | |
| 1.7.5 | 2 / 20 | |
| 1.7.4 | 2 / 20 | |
| 1.7.3 | 2 / 20 | |
| 1.7.2 | 2 / 20 | |
| 1.7.1 | 2 / 20 | |
| 1.7.0 | 2 / 20 | |
| 1.6.0 | 1 / 20 | |
| 1.5.0 | 1 / 20 | |
| 1.4.6 | 1 / 21 | |
| 1.4.5 | 1 / 21 | |
| 1.4.3 | 1 / 21 | |
| 1.4.2 | 1 / 21 | |
| 1.4.1 | 1 / 21 | |
| 1.4.0 | 1 / 21 | |
| 1.3.3 | 1 / 20 | |
| 1.3.2 | 1 / 19 | |
| 1.3.1 | 1 / 19 | |
| 1.3.0 | 1 / 19 | |
| 1.2.1 | 1 / 18 | |
| 1.2.0 | 1 / 18 | |
| 1.1.3 | 1 / 18 | |
| 1.1.2 | 1 / 18 | |
| 1.1.1 | 1 / 18 | |
| 1.1.0 | 1 / 18 | |
| 1.0.1 | 2 / 15 | |
| 1.0.0 | 2 / 15 | |
| 0.4.3 | 2 / 13 | |
| 0.4.2 | 2 / 13 | |
| 0.4.1 | 2 / 13 | |
| 0.4.0 | 2 / 13 | |
| 0.3.3 | 2 / 13 | |
| 0.3.2 | 2 / 13 |
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
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: strml.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: strml.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.