@onekeyfe/hd-transport-http
hardware http transport
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @onekeyfe/* packages; monorepo publish pattern without Sigstore attestation. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 1.1.32 | 4 / 0 | |
| 1.1.31 | 4 / 0 | |
| 1.1.30 | 4 / 0 | |
| 1.1.29 | 4 / 0 | |
| 1.1.28 | 4 / 0 | |
| 1.1.27 | 4 / 0 | |
| 1.1.26 | 4 / 0 | |
| 1.1.25 | 4 / 0 | |
| 1.1.24 | 4 / 0 | |
| 1.1.23 | 4 / 0 | |
| 1.1.22 | 4 / 0 | |
| 1.1.21 | 4 / 0 | |
| 1.1.20 | 4 / 0 | |
| 1.1.19 | 4 / 0 | |
| 1.1.18 | 4 / 0 | |
| 1.1.17 | 4 / 0 | |
| 1.1.16 | 4 / 0 | |
| 1.1.15 | 4 / 0 | |
| 1.1.14 | 4 / 0 | |
| 1.1.13 | 4 / 0 | |
| 1.1.12 | 4 / 0 | |
| 1.1.11 | 4 / 0 | |
| 1.1.10 | 4 / 0 | |
| 1.1.9 | 4 / 0 | |
| 1.1.8 | 4 / 0 | |
| 1.1.7 | 4 / 0 | |
| 1.1.6 | 4 / 0 | |
| 1.1.5 | 4 / 0 | |
| 1.1.3 | 4 / 0 | |
| 1.1.2 | 4 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.37 | 4 / 0 | |
| 1.0.36 | 4 / 0 | |
| 1.0.35 | 4 / 0 | |
| 1.0.34 | 4 / 0 | |
| 1.0.33 | 4 / 0 | |
| 1.0.32 | 4 / 0 | |
| 1.0.31 | 4 / 0 | |
| 1.0.30 | 4 / 0 | |
| 1.0.29 | 4 / 0 | |
| 1.0.28 | 4 / 0 | |
| 1.0.26 | 3 / 0 | |
| 1.0.25 | 3 / 0 | |
| 1.0.24 | 3 / 0 | |
| 1.0.23 | 3 / 0 | |
| 1.0.22 | 3 / 0 | |
| 1.0.21 | 3 / 0 | |
| 1.0.20 | 3 / 0 | |
| 1.0.19 | 3 / 0 | |
| 1.0.18 | 3 / 0 |
v1.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.