@dynamic-labs/ethereum-aa-zksync
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from named account to GitHub Actions CI publisher is a standard DevOps migration for Dynamic Labs packages. | ai | |
| dependencies | unvetted-dep:zksync-sso | AI (dependencies): zksync-sso is the official ZKsync SSO SDK; expected dependency for this AA-ZKsync integration package. | ai | |
| provenance | no-provenance | AI (provenance): Established Dynamic Labs publisher; provenance absence is consistent across their entire package family. | ai | |
| dependencies | unvetted-dep:@dynamic-labs/wallet-book | AI (dependencies): Sibling monorepo package released in lockstep; stable pattern across all @dynamic-labs versions. | ai | |
| dependencies | unvetted-dep:@dynamic-labs/wallet-connector-core | AI (dependencies): Sibling monorepo package released in lockstep; stable pattern across all @dynamic-labs versions. | ai | |
| dependencies | unvetted-dep:@dynamic-labs/ethereum-core | AI (dependencies): Sibling monorepo package released in lockstep; stable pattern across all @dynamic-labs versions. | ai | |
| dependencies | unvetted-dep:@dynamic-labs/ethereum-aa-core | AI (dependencies): Sibling monorepo package released in lockstep; stable pattern across all @dynamic-labs versions. | ai |
Versions (showing 11 of 211)
| Version | Deps | Published |
|---|---|---|
| 4.18.8 | 9 / 0 | |
| 4.18.7 | 9 / 0 | |
| 4.18.6 | 9 / 0 | |
| 4.18.5 | 9 / 0 | |
| 4.18.4 | 9 / 0 | |
| 4.18.3 | 9 / 0 | |
| 4.18.2 | 9 / 0 | |
| 4.18.1 | 9 / 0 | |
| 4.18.0 | 9 / 0 | |
| 4.17.0 | 9 / 0 | |
| 4.16.0 | 9 / 0 |
v4.18.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.