← Home

@kodiak-finance/orderly-wallet-connector-privy

npm

The new wallet connector consists of three parts:

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

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@privy-io/react-auth AI (dependencies): @privy-io/react-auth is a well-known authentication SDK; its use is expected in a privy wallet connector package. ai
bogus-package bogus-package AI (bogus-package): Part of a large @kodiak-finance monorepo release; missing metadata and inflated semver are consistent across the org's packages. ai
phantom-deps phantom-dep:@solana/web3.js AI (phantom-deps): Multi-chain wallet connector; Solana deps conditionally loaded, stable false positive. ai
phantom-deps phantom-dep:@wagmi/connectors AI (phantom-deps): EVM wallet connector; wagmi connectors referenced in config, stable false positive. ai
phantom-deps phantom-dep:@kodiak-finance/orderly-core AI (phantom-deps): Same-org monorepo package; phantom heuristic false positive. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Wallet connector monorepo; lodash declared as utility dep, phantom heuristic false positive. ai
phantom-deps phantom-dep:@solana/wallet-adapter-react-ui AI (phantom-deps): Solana UI adapter; conditionally loaded in multi-chain connector, stable false positive. ai
phantom-deps phantom-dep:@solana-mobile/wallet-adapter-mobile AI (phantom-deps): Mobile Solana adapter; conditionally loaded, stable false positive. ai
phantom-deps phantom-dep:@abstract-foundation/agw-client AI (phantom-deps): Abstract chain integration; conditionally loaded, stable false positive. ai
phantom-deps phantom-dep:@types/lodash AI (phantom-deps): Type-only package; framework-scoped, not directly imported by convention. ai

Versions (showing 38 of 38)

Version Deps Published
2.9.2 23 / 6
2.9.1 23 / 6
2.9.0 23 / 6
2.8.33 23 / 6
2.8.32 23 / 6
2.8.31 23 / 6
2.8.30 23 / 6
2.8.29 23 / 6
2.8.28 23 / 6
2.8.27 23 / 6
2.8.26 23 / 6
2.8.25 23 / 6
2.8.24 23 / 6
2.8.23 23 / 6
2.8.22 23 / 6
2.8.21 23 / 6
2.8.20 23 / 6
2.8.19 23 / 6
2.8.18 23 / 6
2.8.17 23 / 6
2.8.16 23 / 6
2.8.15 23 / 6
2.8.14 23 / 6
2.8.13 23 / 6
2.8.12 23 / 6
2.8.11 23 / 6
2.8.10 23 / 6
2.8.9 23 / 6
2.8.8 23 / 6
2.8.7 23 / 6
2.8.6 23 / 6
2.8.5 23 / 6
2.8.4 23 / 6
2.8.3 23 / 6
2.8.2 23 / 6
2.8.1 23 / 6
2.8.0 23 / 6
2.7.4 23 / 6

v2.9.2

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.31

1 finding
LOW No provenance attestation provenance

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

v2.8.30

1 finding
LOW No provenance attestation provenance

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

v2.8.29

1 finding
LOW No provenance attestation provenance

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

v2.8.28

1 finding
LOW No provenance attestation provenance

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

v2.8.27

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.24

1 finding
LOW No provenance attestation provenance

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

v2.8.23

1 finding
LOW No provenance attestation provenance

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

v2.8.22

1 finding
LOW No provenance attestation provenance

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

v2.8.21

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.18

1 finding
LOW No provenance attestation provenance

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

v2.8.17

1 finding
LOW No provenance attestation provenance

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

v2.8.16

1 finding
LOW No provenance attestation provenance

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

v2.8.15

1 finding
LOW No provenance attestation provenance

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

v2.8.14

1 finding
LOW No provenance attestation provenance

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

v2.8.13

1 finding
LOW No provenance attestation provenance

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

v2.8.12

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bards → xsubject (on 2025-11-14, known maintainer) provenance

This version was published by a different npm account (xsubject) than the most recent previously approved version (bards) on 2025-11-14, but xsubject is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.8.11

1 finding
LOW No provenance attestation provenance

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

v2.8.10

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.5

1 finding
LOW No provenance attestation provenance

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

v2.8.4

1 finding
LOW No provenance attestation provenance

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

v2.8.3

1 finding
LOW No provenance attestation provenance

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

v2.8.2

1 finding
LOW No provenance attestation provenance

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

v2.8.1

1 finding
LOW No provenance attestation provenance

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

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.