@aztec/foundation
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/curves/bls12/field.d.ts | AI (source-diff): TypeScript declaration file for BLS12 field classes; long lines are generated type signatures/JSDoc, not obfuscated code. Stable false positive for this crypto library package. | ai | |
| source-diff | obfuscated-file:dest/curves/bls12/point.d.ts | AI (source-diff): TypeScript declaration file for BLS12 point class; long lines are generated type signatures/JSDoc, not obfuscated code. Stable false positive for this crypto library package. | ai | |
| source-diff | obfuscated-file:dest/curves/bn254/field.d.ts | AI (source-diff): TypeScript declaration file for BN254 field classes; long lines are generated type signatures/JSDoc, not obfuscated code. Stable false positive for this crypto library package. | ai | |
| phantom-deps | phantom-dep:lodash.chunk | AI (phantom-deps): Large monorepo foundation package; deps may be used in specific sub-export paths not caught by static analysis. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeepwith | AI (phantom-deps): Large monorepo foundation package; deps may be used in specific sub-export paths not caught by static analysis. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:leveldown | AI (phantom-deps): Large monorepo foundation package; deps may be used in specific sub-export paths not caught by static analysis. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:pako | AI (phantom-deps): Large monorepo foundation package; deps may be used in specific sub-export paths not caught by static analysis. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Large monorepo foundation package; deps may be used in specific sub-export paths not caught by static analysis. Stable pattern across versions. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in bigint-buffer is standard bigint-to-buffer conversion in a cryptographic foundation library; not malicious payload hiding. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; missing metadata fields are typical for internal monorepo packages. Age, download volume, and version count confirm legitimacy. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in schemas/utils.js is a Zod schema validator for base64 strings — expected pattern in a serialization/schema library. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 22 / 31 | |
| 4.3.0 | 22 / 31 | |
| 4.2.1 | 22 / 31 | |
| 4.2.0 | 22 / 31 | |
| 4.1.3 | 22 / 31 | |
| 4.1.2 | 22 / 31 | |
| 4.1.1 | 22 / 31 | |
| 4.1.0 | 22 / 31 | |
| 4.0.4 | 22 / 31 | |
| 4.0.3 | 22 / 31 | |
| 4.0.2 | 22 / 31 | |
| 4.0.1 | 22 / 31 | |
| 3.0.3 | 22 / 31 | |
| 3.0.2 | 22 / 31 | |
| 3.0.1 | 22 / 31 | |
| 2.1.11 | 22 / 30 | |
| 2.1.9 | 22 / 30 | |
| 2.1.8 | 22 / 30 | |
| 2.1.7 | 22 / 30 | |
| 2.1.6 | 22 / 30 | |
| 2.1.5 | 22 / 30 | |
| 2.1.4 | 22 / 30 | |
| 2.1.3 | 22 / 30 | |
| 2.1.2 | 22 / 30 | |
| 2.0.4 | 20 / 30 |
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
1 findingPackage 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
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.
v4.1.0
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.
v4.0.4
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.
v4.0.3
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.
v4.0.2
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.
v4.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.
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.
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.
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.
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.
v3.0.1
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.
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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.