@aztec/constants
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used in a build-time codegen script to evaluate named constants as BigInt values from a controlled input map. Not a runtime attack surface; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly declared as a direct dependency in package.json; phantom-dep finding is a false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with 902 versions, 11.9k weekly downloads, and 417 days of history. Missing metadata is typical for monorepo packages, not a spam indicator. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 2 / 9 | |
| 4.3.0 | 2 / 9 | |
| 4.2.1 | 2 / 9 | |
| 4.2.0 | 2 / 9 | |
| 4.1.3 | 2 / 9 | |
| 4.1.2 | 2 / 9 | |
| 4.1.1 | 2 / 9 | |
| 4.1.0 | 2 / 9 | |
| 4.0.4 | 2 / 9 | |
| 4.0.3 | 2 / 9 | |
| 4.0.2 | 2 / 9 | |
| 4.0.1 | 2 / 9 | |
| 3.0.3 | 2 / 9 | |
| 3.0.2 | 2 / 9 | |
| 3.0.1 | 2 / 9 | |
| 2.1.11 | 1 / 8 | |
| 2.1.9 | 1 / 8 | |
| 2.1.8 | 1 / 8 | |
| 2.1.7 | 1 / 8 | |
| 2.1.6 | 1 / 8 | |
| 2.1.5 | 1 / 8 | |
| 2.1.4 | 1 / 8 | |
| 2.1.3 | 1 / 8 | |
| 2.1.2 | 1 / 8 | |
| 2.0.4 | 1 / 8 |
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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.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. 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.