@dynamic-labs/aleo
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate namespace placeholder from established Dynamic Labs publisher; stub pattern is intentional. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is used as a placeholder version by Dynamic Labs across their package ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stub/placeholder package from established publisher; missing description is intentional. | ai | |
| dependencies | unvetted-dep:@provablehq/aleo-types | AI (dependencies): Expected Aleo ecosystem dependency; stable alpha version pinned across all @provablehq/* deps. | ai | |
| dependencies | unvetted-dep:@provablehq/aleo-wallet-adaptor-shield | AI (dependencies): Expected Aleo ecosystem dependency; stable alpha version pinned across all @provablehq/* deps. | ai | |
| dependencies | unvetted-dep:@provablehq/aleo-wallet-standard | AI (dependencies): Expected Aleo ecosystem dependency; stable alpha version pinned across all @provablehq/* deps. | ai | |
| dependencies | unvetted-dep:@provablehq/aleo-wallet-adaptor-core | AI (dependencies): Expected Aleo ecosystem dependency; stable alpha version pinned across all @provablehq/* deps. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.84.0 | 13 / 0 | |
| 4.83.1 | 13 / 0 | |
| 4.83.0 | 13 / 0 | |
| 4.82.0 | 13 / 0 | |
| 4.81.0 | 13 / 0 | |
| 4.80.0 | 13 / 0 | |
| 4.79.1 | 9 / 0 | |
| 4.77.3 | 9 / 0 | |
| 4.77.1 | 9 / 0 | |
| 4.74.0 | 9 / 0 | |
| 4.72.0 | 9 / 0 | |
| 4.71.0 | 9 / 0 | |
| 4.67.0 | 9 / 0 | |
| 0.0.0 | 0 / 0 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.