← Home

@gluestack-ui/menu

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

vidhi499rohit_singhviraj-10rayan1810rajat693surajahmedcmeenumakkarmadhavb230100vaibhk002daminipandeyamars29geekgautamsravankumarvelangigluestackadmingeekashwinimayankp06

Keywords

reactnativereact-nativemenugluestack-uiuniversalheadlesstypescriptcomponentandroidiosnextjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainer is a known contributor within the same org; provenance confirms known-maintainer publish. ai
maintainer-change maintainer-removed AI (maintainer-change): Normal team rotation in active monorepo, not paired with suspicious publish behavior. ai
publish-pattern dormant-publish AI (publish-pattern): Long-lived popular package with irregular but legitimate release cadence. ai
phantom-deps phantom-dep:@react-aria/menu AI (phantom-deps): @react-aria/menu is a declared peer/dep used indirectly via @react-native-aria wrappers; stable false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
0.2.43 11 / 10
0.2.42 11 / 10
0.2.41 11 / 10
0.2.40 11 / 10
0.2.39 11 / 10
0.2.38 11 / 10
0.2.37 11 / 10
0.2.36 11 / 10
0.2.35 11 / 10
0.2.34 10 / 10

v0.2.42

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: viraj-10 → gluestackadmin (on 2025-03-03, known maintainer) provenance

This version was published by a different npm account (gluestackadmin) than the most recent previously approved version (viraj-10) on 2025-03-03, but gluestackadmin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.41

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: viraj-10 → gluestackadmin (on 2025-02-19, known maintainer) provenance

This version was published by a different npm account (gluestackadmin) than the most recent previously approved version (viraj-10) on 2025-02-19, but gluestackadmin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.40

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: viraj-10 → madhavb230100 (on 2025-02-18, known maintainer) provenance

This version was published by a different npm account (madhavb230100) than the most recent previously approved version (viraj-10) on 2025-02-18, but madhavb230100 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.39

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: viraj-10 → madhavb230100 (on 2025-02-18, known maintainer) provenance

This version was published by a different npm account (madhavb230100) than the most recent previously approved version (viraj-10) on 2025-02-18, but madhavb230100 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.38

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: viraj-10 → geekgautam (on 2025-02-18, known maintainer) provenance

This version was published by a different npm account (geekgautam) than the most recent previously approved version (viraj-10) on 2025-02-18, but geekgautam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.37

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: viraj-10 → madhavb230100 (on 2024-11-11, known maintainer) provenance

This version was published by a different npm account (madhavb230100) than the most recent previously approved version (viraj-10) on 2024-11-11, but madhavb230100 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.36

1 finding
LOW No provenance attestation provenance

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

v0.2.35

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.

v0.2.34

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.