← Home

@bitgo/sdk-rpc-wrapper

npm Repository Homepage

Bitgo SDK wrapper to handle EVM RPC events

100
Versions
MIT
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): zahin-mohammad is a BitGo org publisher with 62 approved packages; transition appears to be a legitimate internal maintainer change. ai
bogus-package bogus-package AI (bogus-package): Internal SDK module in BitGo monorepo; sparse README and no keywords are expected for this package type. ai

Versions (showing 100 of 153)

Version Deps Published
2.5.26 1 / 3
2.5.25 1 / 3
2.5.23 1 / 3
2.5.22 1 / 3
2.5.21 1 / 3
2.5.20 1 / 3
2.5.19 1 / 3
2.5.18 1 / 3
2.5.17 1 / 3
2.5.16 1 / 3
2.5.15 1 / 3
2.5.14 1 / 3
2.5.13 1 / 3
2.5.12 1 / 3
2.5.11 1 / 3
2.5.10 1 / 3
2.5.9 1 / 3
2.5.8 1 / 3
2.5.7 1 / 3
2.5.6 1 / 3
2.5.5 1 / 3
2.5.4 1 / 3
2.5.3 1 / 3
2.5.2 1 / 3
2.5.1 1 / 3
2.5.0 1 / 3
2.4.9 1 / 3
2.4.8 1 / 3
2.4.7 1 / 3
2.4.6 1 / 3
2.4.5 1 / 3
2.4.4 1 / 3
2.4.3 1 / 3
2.4.2 1 / 3
2.4.1 1 / 3
2.4.0 1 / 3
2.3.24 1 / 3
2.3.22 1 / 3
2.3.21 1 / 3
2.3.20 1 / 3
2.3.19 1 / 3
2.3.18 1 / 3
2.3.17 1 / 3
2.3.16 1 / 3
2.3.15 1 / 3
2.3.14 1 / 3
2.3.13 1 / 3
2.3.12 1 / 3
2.3.11 1 / 3
2.3.10 1 / 3
2.3.9 1 / 3
2.3.8 1 / 3
2.3.7 1 / 3
2.3.6 1 / 3
2.3.5 1 / 3
2.3.4 1 / 3
2.3.3 1 / 3
2.3.2 1 / 3
2.3.1 1 / 3
2.3.0 1 / 3
2.2.4 1 / 3
2.2.3 1 / 3
2.2.2 1 / 3
2.2.1 1 / 3
2.2.0 1 / 3
2.1.15 1 / 3
2.1.14 1 / 3
2.1.13 1 / 3
2.1.12 1 / 3
2.1.11 1 / 3
2.1.10 1 / 3
2.1.9 1 / 3
2.1.8 1 / 3
2.1.7 1 / 3
2.1.6 1 / 3
2.1.5 1 / 3
2.1.4 1 / 3
2.1.3 1 / 3
2.1.2 1 / 3
2.1.1 1 / 3
2.1.0 1 / 3
2.0.83 1 / 3
2.0.82 1 / 3
2.0.81 1 / 3
2.0.80 1 / 3
2.0.79 1 / 3
2.0.78 1 / 3
2.0.77 1 / 3
2.0.76 1 / 3
2.0.75 1 / 3
2.0.74 1 / 3
2.0.73 1 / 3
2.0.72 1 / 3
2.0.71 1 / 3
2.0.70 1 / 3
2.0.69 1 / 3
2.0.68 1 / 3
2.0.67 1 / 3
2.0.66 1 / 3
2.0.65 1 / 3
Showing 100 of 153 Next page →

v2.5.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.25

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.23

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.22

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.21

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.20

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.77

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.76

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.75

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.74

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.73

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.72

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.71

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.70

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.69

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.68

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.67

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.66

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.65

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.