@hap-toolkit/shared-utils
11
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
diydyqevilemonlewiscuteysusanpanyinhunfeixuezycfxyaotaiyangoneyouzi
Keywords
hap-toolkitquickapp
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on minified bundle output; stable false positive for this build-tool utility package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Missing repo/README is a known gap for this long-standing internal toolkit package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 2 / 1 | |
| 2.0.9 | 2 / 1 | |
| 2.0.8 | 2 / 1 | |
| 2.0.7 | 2 / 1 | |
| 2.0.6 | 2 / 1 | |
| 2.0.5 | 2 / 1 | |
| 2.0.4 | 2 / 1 | |
| 2.0.3 | 2 / 1 | |
| 2.0.2 | 2 / 1 | |
| 2.0.1 | 2 / 1 | |
| 2.0.0 | 2 / 1 |
v2.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.
v2.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.