@things-factory/menu-ui
User interface for 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@operato/oops | AI (dependencies): Same ecosystem dependency in a long-established monorepo; pattern is stable across versions. | ai | |
| dependencies | unvetted-dep:@things-factory/form-ui | AI (dependencies): Same org monorepo sibling dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@things-factory/apptool-base | AI (dependencies): Same org monorepo sibling dependency; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org dependency declared for transitive use; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@things-factory/menu-base | AI (phantom-deps): Same-org dependency declared for transitive use; stable false positive for this monorepo package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 9.1.13 | 10 / 0 | |
| 9.1.0 | 10 / 0 | |
| 9.0.41 | 10 / 0 | |
| 9.0.36 | 10 / 0 | |
| 9.0.34 | 10 / 0 | |
| 9.0.25 | 10 / 0 | |
| 9.0.24 | 10 / 0 | |
| 9.0.20 | 10 / 0 | |
| 9.0.5 | 10 / 0 | |
| 9.0.2 | 10 / 0 | |
| 9.0.0 | 10 / 0 | |
| 8.0.64 | 10 / 0 | |
| 8.0.63 | 10 / 0 | |
| 4.3.815 | 9 / 0 | |
| 4.3.695 | 9 / 0 | |
| 4.3.689 | 9 / 0 |
v9.1.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-22, but nalshya113 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.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.815
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.695
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.