@dynamic-labs-connectors/safe-evm
Make sure to install the connector with the correct version (@3 for sdk v3, @4 for sdk v4, etc...): ``` npm install @dynamic-labs-connectors/safe-evm@3 ```
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.6.7 | 2 / 1 | |
| 4.6.6 | 2 / 1 | |
| 4.6.5 | 2 / 1 | |
| 4.6.4 | 2 / 1 | |
| 4.5.0 | 2 / 1 | |
| 4.4.3 | 2 / 1 | |
| 4.4.2 | 2 / 1 | |
| 4.4.1 | 2 / 1 | |
| 4.4.0 | 2 / 1 | |
| 4.3.2 | 2 / 1 | |
| 4.3.1 | 2 / 1 | |
| 4.3.0 | 2 / 1 | |
| 4.2.1 | 2 / 1 |
v4.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.