@aztec/validator-ha-signer
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 | missing-githead | AI (provenance): Monorepo release metadata gap, not a provenance regression; publisher has strong track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party same-org @aztec packages pinned to matching version. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Used in config/schema files, not a real risk. | ai | |
| phantom-deps | phantom-dep:@aztec/ethereum | AI (phantom-deps): Same-org internal dependency. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known TypeScript runtime helper; declaring it as a dependency without direct imports is a standard pattern across TypeScript projects. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 9 / 11 | |
| 5.0.1 | 9 / 11 | |
| 5.0.0 | 9 / 11 | |
| 4.4.0 | 6 / 11 | |
| 4.3.1 | 6 / 11 | |
| 4.3.0 | 6 / 11 | |
| 4.2.1 | 6 / 11 | |
| 4.2.0 | 6 / 11 | |
| 4.1.3 | 6 / 11 | |
| 4.1.2 | 6 / 11 | |
| 4.1.1 | 6 / 11 | |
| 4.1.0 | 6 / 11 | |
| 4.0.4 | 6 / 11 | |
| 4.0.3 | 6 / 11 | |
| 4.0.2 | 6 / 11 | |
| 4.0.1 | 6 / 11 |
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: charlielye.
v5.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: charlielye.
v5.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: charlielye.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.