@aztec/ethereum
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dest/l1_tx_utils/l1_fee_analyzer.d.ts | AI (source-diff): TypeScript declaration file with long lines from complex type signatures — not obfuscated code. Stable false positive for this Ethereum tooling package. | ai | |
| source-diff | encoded-string-file:dest/contracts/multicall.js | AI (source-diff): Long hex string is Multicall3 deployment bytecode — a well-known standard contract. Expected in Ethereum tooling packages. | ai | |
| source-diff | encoded-string-file:dest/forwarder_proxy.js | AI (source-diff): Long hex string is EVM bytecode (FORWARDER_BYTECODE) for a Solidity contract — standard practice in Ethereum development libraries. | ai | |
| source-diff | obfuscated-file:dest/deploy_aztec_l1_contracts.d.ts | AI (source-diff): TypeScript declaration file with long lines due to complex ABI/union types — not obfuscation. Standard pattern for Ethereum tooling packages. | ai | |
| source-diff | obfuscated-file:dest/deploy_l1_contract.d.ts | AI (source-diff): TypeScript declaration file with long lines due to complex type signatures — not obfuscation. Standard pattern for Ethereum tooling packages. | ai | |
| phantom-deps | phantom-dep:@aztec/constants | AI (phantom-deps): Same-org dependency referenced in config; stable pattern for Aztec monorepo packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit dependency of TypeScript compilation output; stable for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is referenced in config files for monorepo build setup; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:@viem/anvil | AI (phantom-deps): @viem/anvil is referenced in config/test setup; expected for Aztec protocol testing. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env when spawning deploy subprocesses is standard tooling behavior for this Ethereum deployment package; not credential exfiltration. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with 1089 versions and 12k weekly downloads; missing README/repo/keywords metadata is typical for internal monorepo packages. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(h.slice(2), 'hex') is standard Ethereum hex-to-bytes conversion on event log data; not malicious payload decoding. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 11 / 13 | |
| 4.3.0 | 11 / 13 | |
| 4.2.1 | 11 / 13 | |
| 4.2.0 | 11 / 13 | |
| 4.1.3 | 11 / 13 | |
| 4.1.2 | 11 / 13 | |
| 4.1.1 | 11 / 13 | |
| 4.1.0 | 11 / 13 | |
| 4.0.4 | 11 / 13 | |
| 4.0.3 | 11 / 13 | |
| 4.0.2 | 11 / 13 | |
| 4.0.1 | 11 / 13 | |
| 3.0.3 | 11 / 13 | |
| 3.0.2 | 11 / 13 | |
| 3.0.1 | 11 / 13 | |
| 2.1.11 | 11 / 12 | |
| 2.1.9 | 11 / 12 | |
| 2.1.8 | 11 / 12 | |
| 2.1.7 | 11 / 12 | |
| 2.1.6 | 11 / 12 | |
| 2.1.5 | 11 / 12 | |
| 2.1.4 | 11 / 12 | |
| 2.1.3 | 11 / 12 | |
| 2.1.2 | 11 / 12 | |
| 2.0.4 | 11 / 12 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
3 findingsSpreading entire process.env into an object — may capture all secrets 27 | const proc = spawn(command, args, { 28 | cwd, > 29 | env: { 30 | ...process.env, 31 | ...env
Spreading entire process.env into an object — may capture all secrets 44 | const proc = spawn(command, args, { 45 | cwd, > 46 | env: { ...process.env, ...env }, 47 | stdio: ['ignore', 'pipe', 'pipe'], 48 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
5 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
5 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
5 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
4 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
4 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.