@dynamic-labs/waas-evm
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 packaging-at-dynamic-labs to GitHub Actions reflects CI/CD automation; consistent with org-wide pipeline change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org sibling at the same version; consistent with Dynamic Labs monorepo release cadence. | ai | |
| provenance | no-provenance | AI (provenance): Dynamic Labs consistently publishes without Sigstore provenance across 233 versions; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large SDK monorepo; sparse README/keywords is a consistent pattern across the @dynamic-labs namespace. | ai |
Versions (showing 6 of 210)
| Version | Deps | Published |
|---|---|---|
| 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.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.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.17.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.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.