@atlaskit/popper
A wrapper for React Popper for situations which require a bespoke popup where other ADS components are deemed unsuitable
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 | dormant-publish | AI (publish-pattern): Atlassian artifact team with strong track record; long dormancy plausible for a stable utility package in a large monorepo. | ai | |
| dependencies | unvetted-dep:@popperjs/core | AI (dependencies): @popperjs/core is the canonical Popper.js v2 library and a legitimate, expected dependency for @atlaskit/popper. No security concerns associated with this dependency. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher has 117 approved packages without provenance; this is a stable publishing pattern for this org, not a risk signal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 3 / 17 | |
| 7.1.10 | 3 / 17 | |
| 7.1.9 | 3 / 16 | |
| 7.1.8 | 3 / 15 | |
| 7.1.7 | 3 / 15 | |
| 7.1.6 | 3 / 16 | |
| 7.1.5 | 3 / 16 | |
| 7.1.4 | 3 / 16 | |
| 7.1.3 | 3 / 16 | |
| 7.1.2 | 3 / 16 | |
| 7.1.1 | 3 / 16 | |
| 7.1.0 | 3 / 17 |
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.