@dynamic-labs/starknet
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:assert | AI (phantom-deps): assert is a declared dependency used for polyfilling; phantom-dep heuristic fires but it's a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:text-encoding | AI (phantom-deps): text-encoding is a declared polyfill dependency; phantom-dep heuristic is a stable false positive here. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): URL is web.argent.xyz — the official Argent web wallet endpoint; not a suspicious TLD in this context. | ai |
Versions (showing 51 of 200)
| Version | Deps | Published |
|---|---|---|
| 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 | 15 / 0 | |
| 4.82.0 | 15 / 0 | |
| 4.81.0 | 15 / 0 | |
| 4.80.0 | 15 / 0 | |
| 4.79.2 | 15 / 0 | |
| 4.79.1 | 15 / 0 | |
| 4.79.0 | 15 / 0 | |
| 4.78.1 | 15 / 0 | |
| 4.78.0 | 15 / 0 | |
| 4.77.4 | 15 / 0 | |
| 4.77.3 | 15 / 0 | |
| 4.77.2 | 15 / 0 | |
| 4.77.1 | 15 / 0 | |
| 4.77.0 | 15 / 0 | |
| 4.76.0 | 15 / 0 | |
| 4.75.0 | 15 / 0 | |
| 4.74.1 | 15 / 0 | |
| 4.74.0 | 15 / 0 | |
| 4.73.2 | 15 / 0 | |
| 4.73.0 | 15 / 0 | |
| 4.72.0 | 15 / 0 | |
| 4.71.0 | 15 / 0 | |
| 4.70.0 | 15 / 0 | |
| 4.69.0 | 15 / 0 | |
| 4.68.0 | 15 / 0 | |
| 4.67.2 | 15 / 0 | |
| 4.67.1 | 15 / 0 | |
| 4.67.0 | 15 / 0 | |
| 4.66.0 | 15 / 0 | |
| 4.65.0 | 15 / 0 | |
| 4.64.0 | 15 / 0 | |
| 4.63.1 | 15 / 0 | |
| 4.63.0 | 15 / 0 | |
| 4.62.0 | 15 / 0 | |
| 4.61.7 | 15 / 0 | |
| 4.61.6 | 15 / 0 | |
| 4.61.5 | 15 / 0 | |
| 4.61.4 | 15 / 0 | |
| 4.61.3 | 15 / 0 | |
| 4.61.2 | 15 / 0 | |
| 4.61.1 | 15 / 0 | |
| 4.61.0 | 15 / 0 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.61.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.