← Home

@sk-web-gui/menu-vertical

npm
4
Versions
—
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

jerkerosatieskaidhskhenrsandalfa96aliceringstromskoliverborgstromskmax.erikssontobbe.nordin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped UI component package in an established org; missing metadata is a style issue, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Established package family; missing description is cosmetic. ai
provenance no-provenance AI (provenance): No provenance is common; no other risk signals present. ai

Versions (showing 4 of 4)

Version Deps Published
2.2.10 5 / 1
2.2.8 5 / 1
2.2.7 5 / 1
2.2.6 5 / 1

v2.2.10

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.

v2.2.8

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.

v2.2.7

1 finding
INFO No provenance attestation provenance

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

v2.2.6

1 finding
INFO No provenance attestation provenance

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