@dnd-kit/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @dnd-kit/core is a scoped package in the @dnd-kit monorepo — a well-known React DnD library. The Levenshtein match to 'cors' is purely coincidental and not a typosquat. | ai | |
| dependencies | unvetted-dep:@dnd-kit/utilities | AI (dependencies): @dnd-kit/utilities is a first-party sibling package in the same @dnd-kit monorepo; unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:@dnd-kit/accessibility | AI (dependencies): @dnd-kit/accessibility is a first-party sibling package in the same @dnd-kit monorepo; unvetted status is a pipeline artifact. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 6.3.1 | 3 / 0 | |
| 6.3.0 | 3 / 0 | |
| 6.2.0 | 3 / 0 | |
| 6.1.0 | 3 / 0 | |
| 6.0.8 | 3 / 0 | |
| 6.0.7 | 3 / 0 | |
| 6.0.6 | 3 / 0 | |
| 6.0.5 | 3 / 0 | |
| 6.0.4 | 3 / 0 | |
| 6.0.3 | 3 / 0 | |
| 6.0.2 | 3 / 0 | |
| 6.0.1 | 3 / 0 | |
| 6.0.0 | 3 / 0 |
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.