@dynamic-labs/stellar
A React SDK for implementing Stellar 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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Initial population of a new connector package; size growth reflects legitimate feature code, not injected payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Same as above — first real release of the Stellar connector; size jump is expected. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Part of @dynamic-labs monorepo; 0.0.0 is a namespace placeholder, not a malicious throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Stub/placeholder package from established @dynamic-labs publisher with 152 approved packages. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): eventemitter3 is a declared runtime dep used transitively; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/wallet-book | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 4.88.1 | 13 / 0 | |
| 4.88.0 | 13 / 0 | |
| 4.87.2 | 13 / 0 | |
| 4.87.1 | 13 / 0 | |
| 4.87.0 | 13 / 0 | |
| 4.86.0 | 13 / 0 | |
| 4.85.0 | 13 / 0 | |
| 4.84.1 | 13 / 0 | |
| 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.2 | 13 / 0 | |
| 4.79.1 | 13 / 0 | |
| 4.79.0 | 13 / 0 | |
| 4.78.1 | 13 / 0 | |
| 4.78.0 | 13 / 0 | |
| 4.77.4 | 13 / 0 | |
| 4.77.3 | 13 / 0 | |
| 4.77.2 | 13 / 0 | |
| 4.77.1 | 13 / 0 | |
| 4.77.0 | 13 / 0 | |
| 4.76.0 | 13 / 0 | |
| 4.75.0 | 13 / 0 | |
| 4.74.1 | 13 / 0 | |
| 4.74.0 | 13 / 0 | |
| 4.73.2 | 13 / 0 | |
| 4.73.0 | 13 / 0 | |
| 4.72.0 | 12 / 0 | |
| 4.71.0 | 12 / 0 | |
| 4.70.0 | 12 / 0 | |
| 4.69.0 | 12 / 0 | |
| 4.68.0 | 12 / 0 | |
| 4.67.2 | 12 / 0 | |
| 4.67.1 | 12 / 0 | |
| 4.67.0 | 12 / 0 | |
| 4.66.0 | 12 / 0 | |
| 4.65.0 | 12 / 0 | |
| 4.64.0 | 12 / 0 | |
| 4.63.1 | 12 / 0 | |
| 4.63.0 | 12 / 0 | |
| 4.62.0 | 12 / 0 | |
| 4.61.7 | 10 / 0 | |
| 4.61.6 | 10 / 0 | |
| 4.61.5 | 10 / 0 | |
| 4.61.4 | 10 / 0 | |
| 4.61.3 | 10 / 0 | |
| 4.61.2 | 10 / 0 | |
| 4.61.1 | 10 / 0 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.