@vuu-ui/vuu-ui-controls
VUU UI Controls
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Large established monorepo with consistent publisher; missing gitHead is a CI environment change, not a malicious indicator. | ai | |
| dependencies | unvetted-dep:@salt-ds/icons | AI (dependencies): Pinned Salt DS design system dep; stable ecosystem dependency for this UI package. | ai | |
| dependencies | unvetted-dep:@salt-ds/styles | AI (dependencies): Pinned Salt DS design system dep; stable ecosystem dependency for this UI package. | ai | |
| dependencies | unvetted-dep:@salt-ds/window | AI (dependencies): Pinned Salt DS design system dep; stable ecosystem dependency for this UI package. | ai | |
| dependencies | unvetted-dep:@vuu-ui/vuu-layout | AI (dependencies): Same-monorepo sibling package at matching version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@vuu-ui/vuu-data-react | AI (dependencies): Same-monorepo sibling package at matching version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@vuu-ui/vuu-table | AI (dependencies): Same-monorepo sibling package at matching version; not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all 305 versions and not a risk indicator here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 2.1.8 | 11 / 3 | |
| 2.1.7 | 11 / 3 | |
| 2.1.6 | 11 / 3 | |
| 2.1.5 | 11 / 3 | |
| 2.1.4 | 11 / 3 | |
| 2.1.3 | 11 / 3 | |
| 2.1.2 | 11 / 3 | |
| 2.1.1 | 11 / 3 | |
| 2.1.0 | 11 / 3 | |
| 2.0.0 | 11 / 3 | |
| 1.0.3 | 11 / 3 | |
| 1.0.2 | 11 / 3 | |
| 0.13.117 | 11 / 3 | |
| 0.13.108 | 11 / 3 | |
| 0.13.100 | 11 / 3 | |
| 0.13.95 | 11 / 3 | |
| 0.13.92 | 11 / 3 | |
| 0.13.90 | 11 / 3 | |
| 0.13.89 | 11 / 3 | |
| 0.13.88 | 11 / 3 | |
| 0.13.84 | 11 / 3 | |
| 0.13.83 | 11 / 3 | |
| 0.13.81 | 11 / 3 | |
| 0.13.76 | 11 / 3 | |
| 0.13.73 | 11 / 3 | |
| 0.13.68 | 11 / 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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.108
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.95
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.89
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.84
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.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.