@hyperse/hps-plugin-update
A workspace dependency updater plugin for the HPS (Hyperse) build system. It automates running npm-check-updates across all packages in a monorepo, with sensible defaults, caching, and Yarn/NPM detection.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hyperse/config-loader | AI (dependencies): Same-org (@hyperse) dependency; consistent with the package's ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Hyperse org packages consistently lack provenance; not a risk signal for this publisher. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 5 / 11 | |
| 0.1.3 | 5 / 11 | |
| 0.1.2 | 5 / 12 | |
| 0.1.1 | 5 / 12 | |
| 0.1.0 | 5 / 11 |
v1.0.0
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.