@dynamic-labs-connectors/sequence-cross-app-evm
The Sequence Cross App EVM connector enables integration with Sequence's cross-app wallet functionality in the Dynamic SDK. It provides a seamless way to interact with Sequence's wallet-as-a-service (WaaS) solution, allowing users to connect their wallets
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-tlds | AI (semgrep): All .xyz URLs are legitimate blockchain testnet explorer endpoints (caldera.xyz RaaS); stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.6.6 | 0 / 5 | |
| 4.6.5 | 0 / 5 | |
| 4.6.4 | 0 / 5 | |
| 4.5.0 | 0 / 5 | |
| 4.4.3 | 0 / 5 | |
| 4.4.2 | 0 / 5 | |
| 4.4.1 | 0 / 5 | |
| 4.4.0 | 0 / 5 | |
| 4.3.2 | 0 / 5 | |
| 4.3.1 | 0 / 5 | |
| 4.3.0 | 0 / 5 | |
| 4.2.1 | 0 / 5 |
v4.6.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.