@atlaskit/pragmatic-drag-and-drop
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Same-org monorepo dependency; stable pattern for Atlassian packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org monorepo dependency; stable pattern for Atlassian packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Types-only entry point; minimal README is expected for internal monorepo packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.8.1 | 3 / 13 | |
| 1.8.0 | 3 / 12 | |
| 1.7.10 | 3 / 12 | |
| 1.7.9 | 3 / 12 | |
| 1.7.8 | 3 / 12 | |
| 1.7.7 | 3 / 11 | |
| 1.7.6 | 3 / 11 | |
| 1.7.5 | 3 / 11 | |
| 1.7.4 | 3 / 13 | |
| 1.7.3 | 3 / 13 | |
| 1.7.2 | 3 / 13 | |
| 1.7.1 | 3 / 13 | |
| 1.7.0 | 5 / 12 | |
| 1.6.1 | 3 / 12 | |
| 1.6.0 | 3 / 12 | |
| 1.5.3 | 3 / 12 |
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.