@dynamic-labs/waas-sui
A React SDK for implementing wallet web3 authentication and authorization to your website.
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 org account to GitHub Actions CI publisher is a documented DevOps migration pattern for Dynamic Labs packages. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/wallet-book | AI (phantom-deps): Same-org monorepo dep; declared but transitively used — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/rpc-providers | AI (phantom-deps): Same-org monorepo dep; declared but transitively used — stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate SDK sub-package in a large monorepo; sparse README is expected for component packages. | ai |
Versions (showing 51 of 206)
| Version | Deps | Published |
|---|---|---|
| 4.88.3 | 15 / 0 | |
| 4.88.2 | 15 / 0 | |
| 4.88.1 | 15 / 0 | |
| 4.88.0 | 15 / 0 | |
| 4.87.2 | 15 / 0 | |
| 4.87.1 | 15 / 0 | |
| 4.87.0 | 15 / 0 | |
| 4.86.0 | 15 / 0 | |
| 4.85.0 | 15 / 0 | |
| 4.84.1 | 15 / 0 | |
| 4.84.0 | 15 / 0 | |
| 4.83.1 | 15 / 0 | |
| 4.83.0 | 14 / 0 | |
| 4.82.0 | 14 / 0 | |
| 4.81.0 | 14 / 0 | |
| 4.80.0 | 14 / 0 | |
| 4.79.2 | 14 / 0 | |
| 4.79.1 | 14 / 0 | |
| 4.79.0 | 14 / 0 | |
| 4.78.1 | 14 / 0 | |
| 4.78.0 | 14 / 0 | |
| 4.77.4 | 14 / 0 | |
| 4.77.3 | 14 / 0 | |
| 4.77.2 | 14 / 0 | |
| 4.77.1 | 14 / 0 | |
| 4.77.0 | 14 / 0 | |
| 4.76.0 | 14 / 0 | |
| 4.75.0 | 14 / 0 | |
| 4.74.1 | 14 / 0 | |
| 4.74.0 | 14 / 0 | |
| 4.73.2 | 14 / 0 | |
| 4.73.0 | 14 / 0 | |
| 4.72.0 | 13 / 0 | |
| 4.71.0 | 13 / 0 | |
| 4.70.0 | 13 / 0 | |
| 4.69.0 | 13 / 0 | |
| 4.68.0 | 13 / 0 | |
| 4.67.2 | 13 / 0 | |
| 4.67.1 | 13 / 0 | |
| 4.67.0 | 13 / 0 | |
| 4.66.0 | 13 / 0 | |
| 4.65.0 | 13 / 0 | |
| 4.64.0 | 13 / 0 | |
| 4.63.1 | 13 / 0 | |
| 4.63.0 | 13 / 0 | |
| 4.62.0 | 13 / 0 | |
| 4.61.7 | 13 / 0 | |
| 4.61.6 | 13 / 0 | |
| 4.61.5 | 13 / 0 | |
| 4.61.4 | 13 / 0 | |
| 4.61.3 | 13 / 0 |
v4.88.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.