← Home

@nsshunt/stsuxvue

STS UX Components for Vue 3 and Vuetify

3
Versions
MIT
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

nsshunt

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:uuid AI (phantom-deps): Component library; deps declared for consumers, not all directly imported in library code. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Same pattern — declared peer/consumer dep, not directly imported in library bundle. ai
phantom-deps phantom-dep:dotenv AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:dompurify AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:apexcharts AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:vue-router AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:ansi-to-html AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:tiny-emitter AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:webfontloader AI (phantom-deps): Same pattern — declared peer/consumer dep. ai
phantom-deps phantom-dep:@nsshunt/stssocketioutils AI (phantom-deps): Same org scope; declared dep not directly imported in library entry point. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.113 21 / 14
1.0.111 21 / 14
1.0.96 21 / 14

v1.0.113

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.

v1.0.111

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.

v1.0.96

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.