@vuu-ui/vuu-shell
VUU UI Shell
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:@vuu-ui/vuu-table | AI (phantom-deps): Same org monorepo package; declared as dep even if not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:@vuu-ui/vuu-data-remote | AI (phantom-deps): Same org monorepo package; declared as dep even if not directly imported in analyzed files. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.8 | 13 / 3 | |
| 2.1.7 | 13 / 3 | |
| 2.1.6 | 13 / 3 | |
| 2.1.5 | 13 / 3 | |
| 2.1.4 | 13 / 3 | |
| 2.1.3 | 13 / 3 | |
| 2.1.2 | 13 / 3 | |
| 2.1.1 | 13 / 3 | |
| 2.1.0 | 13 / 3 | |
| 1.0.3 | 13 / 3 |
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage 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.