@dynamic-labs/ethereum-aa
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 reflects CI/CD automation; stable pattern for this org's SDK packages. | ai | |
| provenance | no-provenance | AI (provenance): Dynamic Labs publishes via GitHub Actions CI without Sigstore attestation; consistent across all versions. | ai |
Versions (showing 89 of 289)
| Version | Deps | Published |
|---|---|---|
| 4.20.7 | 12 / 0 | |
| 4.20.6 | 12 / 0 | |
| 4.20.5 | 12 / 0 | |
| 4.20.4 | 12 / 0 | |
| 4.20.3 | 12 / 0 | |
| 4.20.2 | 12 / 0 | |
| 4.20.1 | 12 / 0 | |
| 4.20.0 | 12 / 0 | |
| 4.19.7 | 12 / 0 | |
| 4.19.6 | 12 / 0 | |
| 4.19.5 | 12 / 0 | |
| 4.19.4 | 12 / 0 | |
| 4.19.3 | 12 / 0 | |
| 4.19.2 | 12 / 0 | |
| 4.19.1 | 12 / 0 | |
| 4.19.0 | 12 / 0 | |
| 4.18.8 | 12 / 0 | |
| 4.18.7 | 12 / 0 | |
| 4.18.6 | 12 / 0 | |
| 4.18.5 | 12 / 0 | |
| 4.18.4 | 12 / 0 | |
| 4.18.3 | 12 / 0 | |
| 4.18.2 | 12 / 0 | |
| 4.18.1 | 12 / 0 | |
| 4.18.0 | 12 / 0 | |
| 4.17.0 | 12 / 0 | |
| 4.16.0 | 12 / 0 | |
| 4.15.0 | 12 / 0 | |
| 4.14.0 | 12 / 0 | |
| 4.13.0 | 12 / 0 | |
| 4.12.4 | 12 / 0 | |
| 4.12.3 | 12 / 0 | |
| 4.12.2 | 12 / 0 | |
| 4.12.1 | 12 / 0 | |
| 4.12.0 | 12 / 0 | |
| 4.11.2 | 11 / 0 | |
| 4.11.1 | 11 / 0 | |
| 4.11.0 | 11 / 0 | |
| 4.10.4 | 11 / 0 | |
| 4.10.3 | 11 / 0 | |
| 4.10.2 | 11 / 0 | |
| 4.10.1 | 11 / 0 | |
| 4.10.0 | 11 / 0 | |
| 4.9.12 | 11 / 0 | |
| 4.9.11 | 11 / 0 | |
| 4.9.10 | 11 / 0 | |
| 4.9.9 | 11 / 0 | |
| 4.9.8 | 11 / 0 | |
| 4.9.7 | 11 / 0 | |
| 4.9.6 | 11 / 0 | |
| 4.9.5 | 11 / 0 | |
| 4.9.4 | 11 / 0 | |
| 4.9.3 | 11 / 0 | |
| 4.9.2 | 11 / 0 | |
| 4.9.1 | 11 / 0 | |
| 4.9.0 | 11 / 0 | |
| 4.8.6 | 11 / 0 | |
| 4.8.5 | 11 / 0 | |
| 4.8.4 | 11 / 0 | |
| 4.8.3 | 11 / 0 | |
| 4.8.2 | 11 / 0 | |
| 4.8.1 | 11 / 0 | |
| 4.8.0 | 11 / 0 | |
| 4.7.2 | 11 / 0 | |
| 4.7.1 | 11 / 0 | |
| 4.7.0 | 11 / 0 | |
| 4.6.3 | 11 / 0 | |
| 4.6.2 | 11 / 0 | |
| 4.6.1 | 11 / 0 | |
| 4.6.0 | 11 / 0 | |
| 4.5.3 | 11 / 0 | |
| 4.5.2 | 11 / 0 | |
| 4.5.1 | 11 / 0 | |
| 4.5.0 | 11 / 0 | |
| 4.4.4 | 11 / 0 | |
| 4.4.3 | 11 / 0 | |
| 4.4.2 | 11 / 0 | |
| 4.4.1 | 11 / 0 | |
| 4.4.0 | 11 / 0 | |
| 4.3.2 | 11 / 0 | |
| 4.3.1 | 11 / 0 | |
| 4.3.0 | 11 / 0 | |
| 4.2.3 | 11 / 0 | |
| 4.2.2 | 11 / 0 | |
| 4.2.1 | 11 / 0 | |
| 4.2.0 | 11 / 0 | |
| 4.1.0 | 11 / 0 | |
| 4.0.1 | 11 / 0 | |
| 4.0.0 | 11 / 0 |
v4.15.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.
v4.14.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.
v4.13.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.
v4.12.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.12.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.12.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.12.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.12.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.
v4.11.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.11.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.11.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.
v4.10.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.10.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.10.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.10.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.10.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.
v4.9.12
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.9.11
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.9.10
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.9.9
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.9.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.9.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.9.6
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.9.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.9.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.9.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.9.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.9.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.9.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.
v4.8.6
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.8.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.8.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.8.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.8.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.8.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.8.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.
v4.7.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.7.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.7.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.
v4.6.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.6.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.6.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.6.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.
v4.5.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.5.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.5.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.5.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.
v4.4.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.4.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.4.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.4.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.4.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.
v4.3.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.3.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.3.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.
v4.2.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.2.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.2.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.2.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.
v4.1.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.
v4.0.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.0.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.