@aztec/wallets
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 publish tooling artifact across all @aztec/* siblings, not tampering. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party sibling package in the same monorepo. | ai | |
| phantom-deps | phantom-dep:@aztec/protocol-contracts | AI (phantom-deps): Same-org sibling package, common false positive in monorepo re-exports. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package from AztecProtocol; missing description is a consistent pattern across the @aztec/* namespace, not a malware indicator. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 10 / 5 | |
| 5.0.1 | 10 / 5 | |
| 5.0.0 | 10 / 5 | |
| 4.4.0 | 9 / 5 | |
| 4.3.1 | 9 / 5 | |
| 4.3.0 | 9 / 5 | |
| 4.2.1 | 9 / 5 | |
| 4.2.0 | 9 / 5 | |
| 4.1.3 | 9 / 5 | |
| 4.1.2 | 9 / 5 | |
| 4.1.1 | 9 / 5 | |
| 4.1.0 | 9 / 5 | |
| 4.0.4 | 9 / 5 | |
| 4.0.3 | 9 / 5 | |
| 4.0.2 | 9 / 5 | |
| 4.0.1 | 9 / 5 |
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.