@hyperse/hps
Next-generation CLI for the Hyperse (HPS) ecosystem. It orchestrates plugins for development, build, deployment, updates, and diagnostics with a consistent developer experience.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @hyperse/hps CLI tool; not a typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @hyperse/hps CLI tool; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @hyperse/hps CLI tool; not a typosquat of qs. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 15 / 14 | |
| 0.1.4 | 15 / 15 | |
| 0.1.3 | 15 / 15 | |
| 0.1.0 | 15 / 14 |
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.