@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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by Atlassian's publishing infra migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): atlaskit replaced by atlassianartifactteam; same org. | ai | |
| provenance | publisher-changed | AI (provenance): Atlassian internal publisher migration; both accounts are Atlassian-owned. | ai | |
| provenance | missing-githead | AI (provenance): Consistent with Atlassian's publish infrastructure change. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate Atlassian org transition from atlaskit to atlassianartifactteam (8317 approved pkgs). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atlassianartifactteam is Atlassian's current publishing account. | 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 | |
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Same-org monorepo dependency; stable pattern for Atlassian packages. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 3 / 13 | |
| 2.0.0 | 3 / 13 | |
| 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 | |
| 1.5.2 | 3 / 12 | |
| 1.5.1 | 3 / 12 | |
| 1.5.0 | 3 / 12 | |
| 1.4.0 | 3 / 12 | |
| 1.3.1 | 3 / 12 | |
| 1.3.0 | 3 / 11 | |
| 1.2.3 | 3 / 11 | |
| 1.2.2 | 3 / 11 | |
| 1.2.1 | 3 / 11 | |
| 1.2.0 | 3 / 11 | |
| 1.1.12 | 3 / 11 | |
| 1.1.11 | 3 / 11 | |
| 1.1.10 | 3 / 11 | |
| 1.1.9 | 3 / 12 | |
| 1.1.8 | 3 / 12 | |
| 1.1.7 | 3 / 12 | |
| 1.1.6 | 3 / 12 | |
| 1.1.5 | 3 / 12 | |
| 1.1.4 | 3 / 12 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-01-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.