@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, 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 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 51 of 253)
| Version | Deps | Published |
|---|---|---|
| 4.94.0 | 9 / 0 | |
| 4.93.1 | 9 / 0 | |
| 4.93.0 | 9 / 0 | |
| 4.92.4 | 9 / 0 | |
| 4.92.3 | 9 / 0 | |
| 4.92.2 | 9 / 0 | |
| 4.92.1 | 9 / 0 | |
| 4.92.0 | 9 / 0 | |
| 4.91.6 | 9 / 0 | |
| 4.91.5 | 9 / 0 | |
| 4.91.4 | 9 / 0 | |
| 4.91.3 | 9 / 0 | |
| 4.91.2 | 9 / 0 | |
| 4.91.1 | 9 / 0 | |
| 4.91.0 | 9 / 0 | |
| 4.90.0 | 9 / 0 | |
| 4.89.0 | 9 / 0 | |
| 4.88.6 | 9 / 0 | |
| 4.88.5 | 9 / 0 | |
| 4.88.4 | 9 / 0 | |
| 4.88.3 | 9 / 0 | |
| 4.88.2 | 9 / 0 | |
| 4.88.1 | 9 / 0 | |
| 4.88.0 | 9 / 0 | |
| 4.87.2 | 9 / 0 | |
| 4.87.1 | 9 / 0 | |
| 4.87.0 | 9 / 0 | |
| 4.86.0 | 9 / 0 | |
| 4.85.0 | 9 / 0 | |
| 4.84.1 | 9 / 0 | |
| 4.84.0 | 9 / 0 | |
| 4.83.1 | 9 / 0 | |
| 4.83.0 | 9 / 0 | |
| 4.82.0 | 9 / 0 | |
| 4.81.0 | 9 / 0 | |
| 4.80.0 | 9 / 0 | |
| 4.79.2 | 9 / 0 | |
| 4.79.1 | 9 / 0 | |
| 4.79.0 | 9 / 0 | |
| 4.78.1 | 9 / 0 | |
| 4.78.0 | 9 / 0 | |
| 4.77.4 | 9 / 0 | |
| 4.77.3 | 9 / 0 | |
| 4.77.2 | 9 / 0 | |
| 4.77.1 | 9 / 0 | |
| 4.77.0 | 9 / 0 | |
| 4.76.0 | 9 / 0 | |
| 4.75.0 | 9 / 0 | |
| 4.74.1 | 9 / 0 | |
| 4.74.0 | 9 / 0 | |
| 4.73.2 | 9 / 0 |
v4.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.93.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.