react-rnd
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:re-resizable | AI (phantom-deps): Core dependency used in bundled lib output, not scannable as import. | ai | |
| phantom-deps | phantom-dep:react-draggable | AI (phantom-deps): Core dependency used in bundled lib output, not scannable as import. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TS runtime helper dependency. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 10.5.3 | 3 / 50 | |
| 10.5.2 | 3 / 50 | |
| 10.5.1 | 3 / 50 | |
| 10.5.0 | 3 / 50 | |
| 10.4.14 | 3 / 50 | |
| 10.4.13 | 3 / 50 | |
| 10.4.12 | 3 / 50 | |
| 10.4.11 | 3 / 50 | |
| 10.4.10 | 3 / 50 | |
| 10.4.9 | 3 / 50 | |
| 10.4.8 | 3 / 50 | |
| 10.4.7 | 3 / 50 | |
| 10.4.6 | 3 / 50 | |
| 10.4.5 | 3 / 50 | |
| 10.4.4 | 3 / 50 | |
| 10.4.3 | 3 / 50 | |
| 10.4.2 | 3 / 51 | |
| 10.4.1 | 3 / 51 | |
| 10.4.0 | 3 / 51 | |
| 10.3.7 | 3 / 51 | |
| 10.3.6 | 3 / 51 | |
| 10.3.5 | 3 / 51 | |
| 10.3.4 | 3 / 51 | |
| 10.3.3 | 3 / 51 | |
| 10.3.2 | 3 / 51 | |
| 10.3.1 | 3 / 51 | |
| 10.3.0 | 3 / 51 | |
| 10.2.5 | 3 / 51 | |
| 10.2.4 | 3 / 51 | |
| 10.2.3 | 3 / 51 | |
| 10.2.2 | 3 / 51 | |
| 10.2.1 | 3 / 51 | |
| 10.2.0 | 3 / 51 | |
| 10.1.10 | 3 / 51 | |
| 10.1.9 | 3 / 51 | |
| 10.1.8 | 3 / 51 | |
| 10.1.7 | 3 / 51 | |
| 10.1.6 | 3 / 51 | |
| 10.1.5 | 3 / 51 | |
| 10.1.4 | 3 / 51 | |
| 10.1.3 | 3 / 51 | |
| 10.1.2 | 3 / 51 | |
| 10.1.1 | 3 / 51 | |
| 10.1.0 | 3 / 51 | |
| 10.0.0 | 3 / 50 |
v10.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.