@vuu-ui/vuu-context-menu
This will be the readme inside /packages
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:@salt-ds/styles | AI (dependencies): @salt-ds/styles is part of the JP Morgan Salt Design System; stable legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@salt-ds/window | AI (dependencies): @salt-ds/window is part of the JP Morgan Salt Design System; stable legitimate dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 169 versions of this monorepo package; not a per-version anomaly. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing repo/keywords/README detail is a consistent pattern across all @vuu-ui packages, not a spam signal. | ai | |
| phantom-deps | phantom-dep:@vuu-ui/vuu-utils | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic commonly misfires on monorepo internal packages. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.1.8 | 4 / 3 | |
| 2.1.7 | 4 / 3 | |
| 2.1.6 | 4 / 3 | |
| 2.1.5 | 4 / 3 | |
| 2.1.4 | 4 / 3 | |
| 2.1.3 | 4 / 3 | |
| 2.1.2 | 4 / 3 | |
| 2.1.1 | 4 / 3 | |
| 2.1.0 | 4 / 3 | |
| 2.0.0 | 4 / 3 | |
| 1.0.3 | 4 / 3 | |
| 1.0.2 | 4 / 3 | |
| 1.0.1 | 4 / 3 | |
| 0.13.118 | 4 / 3 | |
| 0.13.113 | 4 / 3 | |
| 0.13.112 | 4 / 3 | |
| 0.13.110 | 4 / 3 | |
| 0.13.105 | 4 / 3 | |
| 0.13.101 | 4 / 3 | |
| 0.13.100 | 4 / 3 | |
| 0.13.93 | 4 / 3 | |
| 0.13.92 | 4 / 3 | |
| 0.13.90 | 4 / 3 | |
| 0.13.88 | 4 / 3 | |
| 0.13.87 | 4 / 3 | |
| 0.13.86 | 4 / 3 | |
| 0.13.85 | 4 / 3 | |
| 0.13.83 | 4 / 3 | |
| 0.13.82 | 4 / 3 | |
| 0.13.81 | 4 / 3 | |
| 0.13.79 | 4 / 3 | |
| 0.13.77 | 4 / 3 | |
| 0.13.70 | 4 / 3 | |
| 0.13.67 | 4 / 3 |
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
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.
v0.13.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.