@rango-dev/provider-binance MIT 4 versions

@rango-dev/provider-binance

npm

Binance Wallet integration for hub. [Homepage](https://www.binance.com/en/binancewallet) | [Docs](https://developers.binance.com/docs/binance-w3w/introduction)

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yeager-eren

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@rango-dev/signer-evm	AI (dependencies): Same-org @rango-dev namespace dependency; consistent across versions of this package.	ai	2026/04/30
provenance	no-provenance	AI (provenance): Provenance absence is common (~88% of npm); no other risk signals present for this package.	ai	2026/04/28

Versions (showing 4 of 4)

Version	Deps	Published
0.3.0	4 / 0	2026-05-31
0.2.1	4 / 0	2026-05-02
0.2.0	4 / 0	2026-04-29
0.1.0	4 / 0	2025-12-30

v0.3.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

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.