← Home

@patternfly/react-drag-drop

npm Repository Homepage

PatternFly drag and drop solution

15
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

dgutridedlabrecqpatternfly-buildjeff-phillips-18mturleybennypmwczkylebuch8evwilkinschulj12nicolethoenheympzhawkinsdlabajausulivkmcfaul

Keywords

reactpatternflydrag-drop

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): kmcfaul is an established PatternFly contributor; publisher change reflects org-level maintainer rotation, not compromise. ai
phantom-deps phantom-dep:@dnd-kit/modifiers AI (phantom-deps): Declared runtime dep referenced in build/config; not a real phantom dep for this package. ai
phantom-deps phantom-dep:resize-observer-polyfill AI (phantom-deps): Declared runtime dep referenced in build/config; stable false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
6.6.0 7 / 0
6.5.1 7 / 0
6.5.0 7 / 0
6.4.3 7 / 0
6.4.2 7 / 0
6.4.1 7 / 0
6.4.0 7 / 0
6.3.1 7 / 0
6.3.0 7 / 0
6.2.3 7 / 0
6.2.2 7 / 0
6.2.1 7 / 0
6.2.0 7 / 0
6.1.0 7 / 0
6.0.0 7 / 0

v6.6.0

2 findings
HIGH Publisher changed: dlabaj → kmcfaul (on 2026-07-01) provenance

This version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.