← Home

@wistia/vhs

npm Repository Homepage

Visual Hype System - Wistia's opinionated component library for building React UIs

10
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

wistia_engineeringokizersheldonatwistia

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@wistia/vhs-design-tokens AI (phantom-deps): Same-org scoped dep; config-file reference pattern in monorepo is expected. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped @wistia package; Levenshtein match to 'qs' is coincidental, not impersonation. ai
phantom-deps phantom-dep:prettier AI (phantom-deps): prettier is a dev/config tool; phantom-dep false positive for this package. ai
phantom-deps phantom-dep:slate-dom AI (phantom-deps): slate-dom is a legitimate runtime dep; phantom-dep heuristic misfires here. ai
phantom-deps phantom-dep:type-fest AI (phantom-deps): type-fest is a type-only dep; phantom-dep false positive for TypeScript packages. ai
license uncommon-license:UNLICENSED AI (license): Proprietary Wistia internal library; UNLICENSED is intentional and stable. ai

Versions (showing 10 of 10)

Version Deps Published
6.0.0 19 / 48
5.0.5 19 / 48
5.0.4 19 / 49
5.0.3 19 / 49
5.0.2 19 / 48
5.0.1 19 / 50
5.0.0 18 / 48
4.0.3 18 / 48
4.0.2 18 / 48
4.0.1 18 / 48

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.0.5

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.

v5.0.4

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.

v5.0.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.

v5.0.2

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.

v5.0.1

1 finding
LOW No provenance attestation provenance

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

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

v4.0.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.

v4.0.2

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.

v4.0.1

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.