@orderly.network/wallet-connector ISC 32 versions

@orderly.network/wallet-connector

npm

32

Versions

ISC

License

No

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

orderly.productkai.jiangstognievleo_orderlygoogolev

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:rxjs	AI (phantom-deps): rxjs is a common reactive utility; phantom-dep heuristic fires on config-only references in this build-tool package.	ai	2026/05/31
phantom-deps	phantom-dep:@types/lodash	AI (phantom-deps): Type-only package; not directly imported at runtime by convention.	ai	2026/05/31
phantom-deps	phantom-dep:@solana/web3.js	AI (phantom-deps): Solana deps referenced in config/peer context; stable false positive for this wallet connector.	ai	2026/05/31
phantom-deps	phantom-dep:@solana/spl-token	AI (phantom-deps): Same as @solana/web3.js — config-referenced, stable false positive.	ai	2026/05/31
phantom-deps	phantom-dep:@web3-onboard/bitget	AI (phantom-deps): Wallet adapter loaded by convention; stable false positive for this package.	ai	2026/05/31
phantom-deps	phantom-dep:@orderly.network/core	AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive here.	ai	2026/05/31

Versions (showing 32 of 32)

Version	Deps	Published
3.1.0	20 / 4	2026-05-27
3.0.4	20 / 4	2026-05-20
3.0.3	20 / 4	2026-05-07
3.0.2	20 / 4	2026-04-30
3.0.1	20 / 4	2026-04-29
3.0.0	20 / 4	2026-04-28
2.12.4	20 / 4	2026-04-21
2.12.3	20 / 4	2026-04-19
2.12.2	20 / 4	2026-04-14
2.12.1	20 / 4	2026-04-10
2.12.0	20 / 4	2026-04-01
2.11.2	20 / 4	2026-03-24
2.11.1	20 / 4	2026-03-18
2.11.0	20 / 4	2026-03-17
2.10.2	20 / 4	2026-03-16
2.10.1	20 / 4	2026-03-04
2.10.0	20 / 4	2026-03-03
2.9.1	20 / 4	2026-02-14
2.9.0	20 / 4	2026-02-13
2.8.14	20 / 4	2026-02-10
2.8.13	20 / 4	2026-01-30
2.8.12	20 / 4	2026-01-15
2.8.11	20 / 4	2026-01-14
2.8.10	20 / 4	2025-12-23
2.8.9	20 / 4	2025-12-20
2.8.8	20 / 4	2025-12-10
2.8.7	20 / 4	2025-12-09
2.8.6	20 / 4	2025-12-02
2.8.5	20 / 4	2025-11-26
2.8.4	20 / 4	2025-11-25
2.8.3	20 / 4	2025-11-19
2.8.2	20 / 4	2025-11-12

v3.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.

v3.0.4

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.

v3.0.3

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.

v3.0.2

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.

v3.0.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.

v2.12.4

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.12.3

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.12.2

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.12.1

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.12.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.

v2.11.2

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.11.1

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.11.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.

v2.10.2

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.10.1

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.10.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.

v2.9.1

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.9.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.

v2.8.14

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.8.13

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.8.12

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.8.11

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.8.10

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.8.9

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.8.8

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.8.7

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.8.6

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.8.5

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.8.4

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.8.3

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.8.2

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.