← Home

@tamagui/popover

npm
28
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

nwienert

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Tamagui does not publish with Sigstore provenance; consistent across all versions. ai
dependencies unvetted-dep:@tamagui/adapt AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
dependencies unvetted-dep:@tamagui/sheet AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
dependencies unvetted-dep:@tamagui/popper AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
dependencies unvetted-dep:@tamagui/portal AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
dependencies unvetted-dep:@tamagui/animate AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
dependencies unvetted-dep:@tamagui/animate-presence AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
phantom-deps phantom-dep:react-freeze AI (phantom-deps): react-freeze is a declared runtime dep used indirectly via sheet/scroll; stable false positive. ai
dependencies unvetted-dep:@tamagui/dismissable AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
dependencies unvetted-dep:@tamagui/focus-scope AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. ai
bogus-package bogus-package AI (bogus-package): Tamagui monorepo sub-package; missing metadata is normal for this ecosystem. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package; missing description is stable and benign. ai

Versions (showing 28 of 28)

Version Deps Published
2.1.0 20 / 3
2.0.0 20 / 3
1.144.4 21 / 3
1.144.3 21 / 3
1.144.2 21 / 3
1.144.0 21 / 3
1.143.1 21 / 3
1.142.0 21 / 3
1.141.5 21 / 3
1.141.4 21 / 3
1.141.0 21 / 3
1.140.2 21 / 3
1.140.0 21 / 3
1.139.3 21 / 3
1.139.2 21 / 3
1.139.0 21 / 3
1.138.5 21 / 3
1.138.3 21 / 3
1.138.2 21 / 3
1.138.1 21 / 3
1.137.3 21 / 3
1.137.1 21 / 3
1.136.7 21 / 3
1.136.6 21 / 3
1.136.4 21 / 3
1.136.3 21 / 3
1.136.1 21 / 3
1.136.0 21 / 3

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.144.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.144.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.144.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.144.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.143.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.142.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.141.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.141.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.141.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.140.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.140.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.139.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.139.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.139.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.138.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.138.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.138.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.138.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.137.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.137.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.