@atlaskit/popup
A popup displays brief content in an overlay.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @atlaskit scope; consistent with Atlaskit's internal package decomposition pattern. | ai | |
| dependencies | unvetted-dep:@atlaskit/motion | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; expected internal dependency for this UI component. | ai | |
| dependencies | unvetted-dep:@atlaskit/popper | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; expected internal dependency for a popup component. | ai | |
| dependencies | unvetted-dep:@atlaskit/portal | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; expected internal dependency for a popup component. | ai | |
| dependencies | unvetted-dep:@atlaskit/css | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; expected internal dependency for this UI component. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; expected internal dependency for this UI component. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; expected internal dependency for feature flagging. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same org scope (@atlaskit); phantom dep finding is benign for intra-monorepo packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Sibling @atlaskit/* package from the same Atlassian org; standard design token dependency. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 4.23.0 | 16 / 26 | |
| 4.22.1 | 16 / 26 | |
| 4.22.0 | 16 / 26 | |
| 4.21.2 | 16 / 26 | |
| 4.21.1 | 16 / 26 | |
| 4.21.0 | 16 / 26 | |
| 4.20.2 | 16 / 26 | |
| 4.20.1 | 16 / 25 | |
| 4.20.0 | 16 / 25 | |
| 4.19.1 | 16 / 25 | |
| 4.19.0 | 16 / 25 | |
| 4.18.0 | 16 / 25 | |
| 4.17.0 | 15 / 24 | |
| 4.16.6 | 15 / 24 | |
| 4.16.5 | 15 / 24 | |
| 4.16.4 | 15 / 24 | |
| 4.16.3 | 15 / 24 | |
| 4.16.2 | 15 / 23 | |
| 4.16.1 | 15 / 23 | |
| 4.16.0 | 15 / 23 | |
| 4.15.0 | 15 / 23 | |
| 4.14.0 | 14 / 23 | |
| 4.13.4 | 14 / 22 | |
| 4.13.3 | 14 / 22 | |
| 4.13.2 | 14 / 22 | |
| 4.13.1 | 14 / 22 | |
| 4.13.0 | 14 / 23 | |
| 4.12.0 | 14 / 23 | |
| 4.11.0 | 14 / 23 | |
| 4.10.0 | 14 / 23 | |
| 4.9.0 | 14 / 23 | |
| 4.8.3 | 14 / 23 | |
| 4.8.2 | 14 / 23 | |
| 4.8.1 | 14 / 23 | |
| 4.8.0 | 14 / 23 | |
| 4.7.1 | 14 / 23 | |
| 4.7.0 | 14 / 23 | |
| 4.6.5 | 14 / 23 | |
| 4.6.4 | 14 / 24 | |
| 4.6.3 | 14 / 24 | |
| 4.6.2 | 14 / 24 | |
| 4.6.1 | 14 / 24 | |
| 4.6.0 | 14 / 24 | |
| 4.5.0 | 14 / 24 | |
| 4.4.5 | 14 / 24 | |
| 4.4.4 | 14 / 24 | |
| 4.4.3 | 14 / 24 | |
| 4.4.2 | 14 / 24 | |
| 4.4.1 | 14 / 24 | |
| 4.4.0 | 14 / 24 | |
| 4.3.15 | 14 / 24 | |
| 4.3.14 | 14 / 24 | |
| 4.3.13 | 14 / 24 | |
| 4.3.12 | 14 / 24 | |
| 4.3.11 | 14 / 24 | |
| 4.3.10 | 14 / 24 | |
| 4.3.9 | 14 / 24 | |
| 4.3.8 | 14 / 24 | |
| 4.3.7 | 14 / 25 | |
| 4.3.6 | 14 / 25 | |
| 4.3.5 | 14 / 25 | |
| 4.3.4 | 14 / 26 | |
| 4.3.3 | 14 / 26 | |
| 4.3.2 | 14 / 26 | |
| 4.3.1 | 14 / 26 | |
| 4.3.0 | 14 / 26 | |
| 4.2.0 | 14 / 26 |
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.