@aztec/txe
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 process; consistent with unchanged provenance direction. | ai | |
| source-diff | obfuscated-file:dest/HandshakeRegistry-KKUEU7XW.js | AI (source-diff): Bundled Noir contract artifact. | ai | |
| source-diff | obfuscated-file:dest/MultiCallEntrypoint-TGICA67H.js | AI (source-diff): Bundled Noir contract artifact. | ai | |
| source-diff | obfuscated-file:dest/AuthRegistry-FSRZIMX6.js | AI (source-diff): Bundled Noir contract artifact (bytecode/ABI), not obfuscation. | ai | |
| source-diff | net-exec-file:dest/chunk-PDOEF22H.js | AI (source-diff): esbuild-bundled third-party deps (vary, etc.), not a dropper. | ai | |
| source-diff | net-exec-file:dest/chunk-YP4ODNMQ.js | AI (source-diff): esbuild-bundled sha3/crypto deps, not a dropper. | ai | |
| source-diff | obfuscated-file:dest/ContractClassRegistry-N6NA3SFA.js | AI (source-diff): Bundled Noir contract artifact. | ai | |
| source-diff | obfuscated-file:dest/ContractInstanceRegistry-NADDSLGL.js | AI (source-diff): Bundled Noir contract artifact. | ai | |
| source-diff | obfuscated-file:dest/FeeJuice-QBH5JWJV.js | AI (source-diff): Bundled Noir contract artifact. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the @aztec monorepo; missing metadata (description, repo URL, keywords) is typical for internal scoped packages in large monorepos, not a spam/malware indicator. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of cryptographic field elements (Fr) is standard and expected in a ZK/blockchain library like @aztec/txe. Not a malicious payload indicator. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 18 / 9 | |
| 4.4.0 | 15 / 8 | |
| 4.3.1 | 15 / 8 | |
| 4.3.0 | 15 / 8 | |
| 4.2.1 | 15 / 8 | |
| 4.2.0 | 15 / 8 | |
| 4.1.3 | 15 / 8 | |
| 4.1.2 | 15 / 8 | |
| 4.1.1 | 15 / 8 | |
| 4.1.0 | 15 / 8 | |
| 4.0.4 | 15 / 8 | |
| 4.0.3 | 15 / 8 | |
| 4.0.2 | 15 / 8 | |
| 4.0.1 | 15 / 8 | |
| 3.0.3 | 15 / 8 | |
| 3.0.2 | 15 / 8 | |
| 3.0.1 | 15 / 8 | |
| 2.1.11 | 15 / 7 | |
| 2.1.9 | 15 / 7 | |
| 2.1.8 | 15 / 7 | |
| 2.1.7 | 15 / 7 | |
| 2.1.6 | 15 / 7 | |
| 2.1.5 | 15 / 7 | |
| 2.1.4 | 15 / 7 | |
| 2.1.3 | 15 / 7 | |
| 2.1.2 | 15 / 7 | |
| 2.0.4 | 15 / 7 |
v5.0.0
12 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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.