@dynamic-labs/wallet-book
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): Dynamic Labs migrated publishing to GitHub Actions CI; consistent with org-level automation, not a suspicious takeover. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): util is a declared runtime dependency in package.json; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all Dynamic Labs releases; published via GitHub Actions, low risk for this org. | ai |
Versions (showing 8 of 209)
| Version | Deps | Published |
|---|---|---|
| 4.18.5 | 7 / 0 | |
| 4.18.4 | 7 / 0 | |
| 4.18.3 | 7 / 0 | |
| 4.18.2 | 7 / 0 | |
| 4.18.1 | 7 / 0 | |
| 4.18.0 | 7 / 0 | |
| 4.17.0 | 7 / 0 | |
| 4.16.0 | 7 / 0 |
v4.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.