← Home

@web3-onboard/bitget

npm Repository Homepage
2
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

aaronbarnard1cmeisl

Keywords

EthereumWeb3EVMdappMultichainWalletTransactionProviderHardware WalletNotificationsReactSvelteVueNextNuxtMetaMaskCoinbaseWalletConnectLedgerTrezorConnect WalletEthereum HooksBlocknativeMempoolpendingconfirmedInjected WalletCryptoCrypto WalletEnkryptBitget Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Blocknative monorepo packages consistently lack provenance; not a meaningful risk signal here. ai

Versions (showing 2 of 2)

Version Deps Published
2.1.1 2 / 2
2.1.0 2 / 2

v2.1.0

1 finding
INFO No provenance attestation provenance

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