@kodiak-finance/orderly-wallet-connector ISC 39 versions

@kodiak-finance/orderly-wallet-connector

npm

39

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

bearticxsubjectberastotlebards

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 peer/transitive dep in reactive wallet libs; phantom-dep heuristic false positive for this package.	ai	2026/05/18
phantom-deps	phantom-dep:@types/lodash	AI (phantom-deps): Type-only package; not directly imported by convention, stable false positive.	ai	2026/05/18
phantom-deps	phantom-dep:@solana/web3.js	AI (phantom-deps): Solana deps used transitively via wallet adapter chain; phantom-dep false positive.	ai	2026/05/18
phantom-deps	phantom-dep:@solana/spl-token	AI (phantom-deps): Same as @solana/web3.js — transitive wallet adapter usage.	ai	2026/05/18
phantom-deps	phantom-dep:@web3-onboard/bitget	AI (phantom-deps): Wallet connector loaded by convention/config, not direct import; stable false positive.	ai	2026/05/18
phantom-deps	phantom-dep:@kodiak-finance/orderly-core	AI (phantom-deps): Same-org sibling package; likely re-exported or used indirectly, stable false positive.	ai	2026/05/18

Versions (showing 39 of 39)

Version	Deps	Published
2.9.3	20 / 4	2026-06-08
2.9.2	20 / 4	2026-05-06
2.9.1	20 / 4	2026-04-24
2.9.0	20 / 4	2026-04-01
2.8.33	20 / 4	2026-03-18
2.8.32	20 / 4	2026-03-05
2.8.31	20 / 4	2026-02-19
2.8.30	20 / 4	2026-02-05
2.8.29	20 / 4	2026-01-21
2.8.28	20 / 4	2026-01-07
2.8.27	20 / 4	2026-01-06
2.8.26	20 / 4	2026-01-06
2.8.25	20 / 4	2026-01-05
2.8.24	20 / 4	2025-12-31
2.8.23	20 / 4	2025-12-31
2.8.22	20 / 4	2025-12-29
2.8.21	20 / 4	2025-12-17
2.8.20	20 / 4	2025-12-12
2.8.19	20 / 4	2025-12-12
2.8.18	20 / 4	2025-12-09
2.8.17	20 / 4	2025-11-30
2.8.16	20 / 4	2025-11-25
2.8.15	20 / 4	2025-11-19
2.8.14	20 / 4	2025-11-17
2.8.13	20 / 4	2025-11-14
2.8.12	20 / 4	2025-11-14
2.8.11	20 / 4	2025-11-12
2.8.10	20 / 4	2025-11-07
2.8.9	20 / 4	2025-11-07
2.8.8	20 / 4	2025-11-07
2.8.7	20 / 4	2025-11-05
2.8.6	20 / 4	2025-11-04
2.8.5	20 / 4	2025-11-03
2.8.4	20 / 4	2025-10-28
2.8.3	20 / 4	2025-10-26
2.8.2	20 / 4	2025-10-21
2.8.1	20 / 4	2025-10-16
2.8.0	20 / 4	2025-10-15
2.7.4	20 / 4	2025-10-13

v2.9.3

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

v2.8.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.8.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.7.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.