← Home

@atlaskit/pragmatic-drag-and-drop-react-drop-indicator

npm Repository Homepage

An optional Pragmatic drag and drop package containing react components that provide a visual indication about what the user will achieve when the drop (eg lines)

17
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Atlaskit sub-packages routinely have minimal READMEs and no keywords; this is a cosmetic pattern across the entire @atlaskit monorepo, not a spam indicator. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same-org @atlaskit scope phantom dep; common monorepo pattern where deps are used indirectly or as peer deps. ai
phantom-deps phantom-dep:@atlaskit/pragmatic-drag-and-drop AI (phantom-deps): Same-org @atlaskit scope phantom dep; common monorepo pattern where deps are used indirectly or as peer deps. ai

Versions (showing 17 of 17)

Version Deps Published
3.2.16 5 / 7
3.2.15 5 / 6
3.2.14 5 / 6
3.2.13 5 / 6
3.2.12 5 / 6
3.2.11 5 / 6
3.2.10 5 / 6
3.2.9 5 / 6
3.2.8 5 / 6
3.2.7 5 / 6
3.2.6 5 / 6
3.2.5 5 / 7
3.2.4 5 / 7
3.2.3 5 / 8
3.2.2 5 / 7
3.2.1 5 / 7
3.2.0 5 / 7

v3.2.16

1 finding
LOW No provenance attestation provenance

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

v3.2.15

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.

v3.2.14

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.

v3.2.13

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.

v3.2.12

1 finding
LOW No provenance attestation provenance

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

v3.2.11

1 finding
LOW No provenance attestation provenance

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

v3.2.10

1 finding
LOW No provenance attestation provenance

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

v3.2.9

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.