@atlaskit/pragmatic-drag-and-drop-live-region
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Org-wide publisher migration to atlassianartifactteam, consistent across Atlassian's package fleet. | ai | |
| provenance | publisher-changed | AI (provenance): Same org-wide account migration, not a hijack indicator. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Standard Babel runtime helper, loaded by convention. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 9 | |
| 1.4.0 | 1 / 9 | |
| 1.3.4 | 1 / 8 | |
| 1.3.3 | 1 / 8 | |
| 1.3.2 | 1 / 7 | |
| 1.3.1 | 1 / 8 | |
| 1.3.0 | 1 / 9 | |
| 1.2.0 | 1 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.7 | 1 / 9 |
v1.3.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.2.0
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). 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 2024-12-09. 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.