← Home

@cyberpunk-vue/components

npm Repository Homepage

Cyberpunk Vue components - A futuristic Vue 3 component library

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

juxest

Keywords

vuevue3componentsuicyberpunkfuturisticneondesign-system

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@floating-ui/dom AI (phantom-deps): Declared runtime dep in a UI component library; likely used indirectly via bundled components. ai
phantom-deps phantom-dep:@cyberpunk-vue/theme-chalk AI (phantom-deps): Same-org scoped package; likely re-exported or used at runtime without direct import in analyzed files. ai

Versions (showing 7 of 107)

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

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.5

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. Consider requesting the maintainer enable provenance via CI/CD.

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.