@tamagui/create-menu
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tamagui/popover | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@tamagui/get-token | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for bundled packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is common for @tamagui internal packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals explained by monorepo sub-package pattern (no repo link, no keywords, inflated semver). | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 19 / 3 | |
| 2.2.0 | 19 / 3 | |
| 2.1.0 | 19 / 3 | |
| 2.0.0 | 19 / 3 | |
| 1.0.1 | 19 / 3 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.