@page-speed/video
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped React video component; name similarity to vite is coincidental, not impersonation. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 1 / 17 | |
| 0.0.8 | 1 / 17 | |
| 0.0.7 | 1 / 17 | |
| 0.0.6 | 1 / 17 | |
| 0.0.5 | 1 / 17 | |
| 0.0.4 | 1 / 17 | |
| 0.0.3 | 1 / 17 | |
| 0.0.2 | 1 / 17 | |
| 0.0.1 | 1 / 17 |
v0.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jordanhudgens) than the most recent previously approved version (opensiteautomation) on 2026-07-25, but jordanhudgens is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jordanhudgens) than the most recent previously approved version (opensiteautomation) on 2026-07-25, but jordanhudgens is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.