react-dnd
Drag and Drop for React
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:react-dom | AI (typosquat): react-dnd is a well-established drag-and-drop library (4200+ days old, 140 versions). 'dnd' = drag-and-drop, not a typo of react-dom. False positive for this package. | ai | |
| phantom-deps | phantom-dep:hoist-non-react-statics | AI (phantom-deps): hoist-non-react-statics is a legitimate runtime dependency declared in package.json; indirect usage pattern is normal for this library. | ai | |
| bogus-package | bogus-package | AI (bogus-package): react-dnd is a well-known, long-established library. README/keyword signals are cosmetic and do not indicate spam or low-value content. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 16.0.1 | 5 / 17 | |
| 16.0.0 | 5 / 17 | |
| 15.1.2 | 5 / 15 | |
| 15.1.1 | 5 / 15 | |
| 15.1.0 | 5 / 15 | |
| 15.0.2 | 5 / 14 | |
| 15.0.1 | 5 / 11 | |
| 15.0.0 | 5 / 13 |
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.