@vuu-ui/vuu-filters
## Filter
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/lab | AI (dependencies): salt-ds/lab is the pre-release channel of the Salt Design System; alpha versioning is intentional and not a security risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all @vuu-ui/* packages; consistent publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is normal for @vuu-ui packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Low scores from missing metadata typical of monorepo sub-packages; not spam. | ai | |
| phantom-deps | phantom-dep:@vuu-ui/vuu-filter-parser | AI (phantom-deps): Same-org dependency declared in package.json; likely used transitively or in type-only imports within the monorepo. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.1.6 | 11 / 4 | |
| 2.1.1 | 11 / 4 | |
| 2.0.0 | 11 / 4 | |
| 0.13.117 | 11 / 4 | |
| 0.13.85 | 11 / 4 | |
| 0.13.69 | 10 / 4 | |
| 0.13.68 | 10 / 4 |
v2.1.6
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.69
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.