@aztec/epoch-cache
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package inheriting metadata from root package.json; missing description/repo/keywords is a structural pattern, not a spam/malware indicator for @aztec/* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; description is inherited from root config. Not a malware signal for this well-established package family. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dependency; phantom detection is a stable false positive for TypeScript monorepos. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Referenced in config files in a monorepo workspace; workspace hoisting explains the phantom detection. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Referenced in config files in a monorepo workspace; workspace hoisting explains the phantom detection. | ai | |
| phantom-deps | phantom-dep:get-port | AI (phantom-deps): Referenced in config files in a monorepo workspace; workspace hoisting explains the phantom detection. | ai | |
| phantom-deps | phantom-dep:@viem/anvil | AI (phantom-deps): Referenced in config files in a monorepo workspace; workspace hoisting explains the phantom detection. | ai | |
| phantom-deps | phantom-dep:jest-mock-extended | AI (phantom-deps): Referenced in config files in a monorepo workspace; workspace hoisting explains the phantom detection. | ai | |
| phantom-deps | phantom-dep:@aztec/l1-artifacts | AI (phantom-deps): Same-org monorepo package; phantom detection is a stable false positive for @aztec/* workspace packages. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 11 / 7 | |
| 4.3.0 | 11 / 7 | |
| 4.2.1 | 11 / 7 | |
| 4.2.0 | 11 / 7 | |
| 4.1.3 | 11 / 7 | |
| 4.1.2 | 11 / 7 | |
| 4.1.1 | 11 / 7 | |
| 4.1.0 | 11 / 7 | |
| 4.0.4 | 11 / 7 | |
| 4.0.3 | 11 / 7 | |
| 4.0.2 | 11 / 7 | |
| 4.0.1 | 11 / 7 | |
| 3.0.3 | 11 / 7 | |
| 3.0.2 | 11 / 7 | |
| 3.0.1 | 11 / 7 | |
| 2.1.11 | 11 / 6 | |
| 2.1.9 | 11 / 6 | |
| 2.1.8 | 11 / 6 | |
| 2.1.7 | 11 / 6 | |
| 2.1.6 | 11 / 6 | |
| 2.1.5 | 11 / 6 | |
| 2.1.4 | 11 / 6 | |
| 2.1.3 | 11 / 6 | |
| 2.1.2 | 11 / 6 | |
| 2.0.4 | 11 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.4
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.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.6
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.