← Home

@volue/wave-cli

npm Repository

CLI tool for Wave Design System

8
Versions
UNLICENSED
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

fima1uzborg950it.management

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Established @volue org monorepo package; 0.0.0 is a workspace versioning convention, not a throwaway. ai
phantom-deps phantom-dep:@volue/design-icons AI (phantom-deps): Same-org scoped dep; likely used indirectly via build output rather than direct import. ai
phantom-deps phantom-dep:@volue/design-media-queries AI (phantom-deps): Same-org scoped dep; likely used indirectly via build output rather than direct import. ai
phantom-deps phantom-dep:cleye AI (phantom-deps): CLI framework dep; referenced in config/build artifacts, stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.1.6 3 / 14
0.1.5 3 / 14
0.1.4 3 / 14
0.1.3 3 / 14
0.1.2 3 / 14
0.1.1 3 / 14
0.1.0 3 / 14
0.0.0 3 / 14

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.