@3mo/popover
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@3mo/focus-controller | AI (phantom-deps): Same-org monorepo dependency; likely used transitively or via type-only imports. | ai | |
| phantom-deps | phantom-dep:@3mo/pointer-controller | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for this package structure. | ai | |
| phantom-deps | phantom-dep:@a11d/non-inertable-component | AI (phantom-deps): Referenced in config files per finding; not a true phantom dep for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.9.13 | 11 / 1 | |
| 0.9.12 | 11 / 1 | |
| 0.9.11 | 11 / 1 | |
| 0.9.10 | 11 / 1 | |
| 0.9.9 | 11 / 1 | |
| 0.9.8 | 11 / 1 | |
| 0.9.7 | 11 / 1 | |
| 0.9.6 | 11 / 1 | |
| 0.9.5 | 11 / 1 | |
| 0.9.4 | 11 / 1 | |
| 0.9.3 | 11 / 1 | |
| 0.9.2 | 11 / 1 | |
| 0.9.1 | 11 / 1 | |
| 0.9.0 | 11 / 1 | |
| 0.8.4 | 12 / 1 | |
| 0.8.3 | 12 / 1 | |
| 0.8.2 | 12 / 1 | |
| 0.8.1 | 12 / 1 |
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.