@atlaskit/pragmatic-drag-and-drop-react-drop-indicator
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)
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlassian/react-compiler-gating | AI (phantom-deps): Same Atlassian org scope; config-only reference, not a runtime import risk. | ai | |
| 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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 6 / 7 | |
| 4.1.0 | 6 / 7 | |
| 4.0.1 | 6 / 7 | |
| 4.0.0 | 5 / 8 | |
| 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 | |
| 3.1.0 | 5 / 7 | |
| 3.0.2 | 5 / 7 | |
| 3.0.1 | 5 / 7 | |
| 3.0.0 | 5 / 7 |
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.