@aztec/archiver
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dest/archiver.d.ts | AI (source-diff): tsc-generated .d.ts with long type lines, not obfuscated JS. | ai | |
| source-diff | obfuscated-file:dest/modules/data_source_base.d.ts | AI (source-diff): tsc-generated .d.ts, plain readable declarations. | ai | |
| source-diff | obfuscated-file:dest/l1/data_retrieval.d.ts | AI (source-diff): tsc-generated .d.ts, plain readable declarations. | ai | |
| source-diff | obfuscated-file:dest/l1/calldata_retriever.d.ts | AI (source-diff): tsc-generated .d.ts, plain readable declarations. | ai | |
| source-diff | obfuscated-file:dest/store/block_store.d.ts | AI (source-diff): tsc-generated .d.ts, plain readable declarations. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo publish quirk, no provenance regression, no malicious behavior evident. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org @aztec sibling package at matching version. | ai | |
| phantom-deps | phantom-dep:lodash.groupby | AI (phantom-deps): Config-referenced, not a real risk. | ai | |
| phantom-deps | phantom-dep:tsc-watch | AI (phantom-deps): tsc-watch is referenced in config/scripts but not imported at runtime; stable false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in this package is standard Ethereum 0x-prefixed hex-to-bytes conversion for on-chain event data. This is a stable false positive for blockchain tooling. | ai | |
| dependencies | unvetted-dep:tsc-watch | AI (dependencies): tsc-watch is a well-known TypeScript watch utility; its presence in dependencies (vs devDependencies) is a packaging quirk, not a security risk, and it is not directly imported. | ai | |
| dependencies | unvetted-dep:@aztec/noir-protocol-circuits-types | AI (dependencies): Same-org (@aztec) dependency pinned to the exact same version as this package; consistent with monorepo release pattern. Not an independent risk. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declaring it as a dependency without direct imports is a common TypeScript monorepo pattern. | ai | |
| provenance | no-provenance | AI (provenance): Aztec Protocol packages consistently lack Sigstore provenance; this is a stable characteristic of the package ecosystem, not a per-version concern. | ai | |
| phantom-deps | phantom-dep:lodash.omit | AI (phantom-deps): lodash.omit is a utility declared in package.json and referenced in config; benign phantom dep for this package. | ai | |
| phantom-deps | phantom-dep:@aztec/noir-protocol-circuits-types | AI (phantom-deps): Same-org sibling package from the Aztec monorepo; phantom dep pattern is expected in coordinated monorepo releases. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 18 / 11 | |
| 4.2.1 | 17 / 11 | |
| 4.2.0 | 17 / 11 | |
| 4.1.3 | 17 / 11 | |
| 4.1.2 | 17 / 11 | |
| 4.0.4 | 17 / 11 | |
| 4.0.3 | 17 / 11 | |
| 4.0.2 | 17 / 11 | |
| 3.0.3 | 17 / 11 | |
| 3.0.1 | 17 / 11 | |
| 2.1.8 | 17 / 10 | |
| 2.1.6 | 17 / 10 | |
| 2.1.5 | 17 / 10 | |
| 2.1.3 | 17 / 10 | |
| 2.1.2 | 17 / 10 | |
| 2.0.4 | 17 / 10 |
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.