← Home

@morpho-org/liquidation-sdk-viem

Viem-based package that provides utilities to build viem-based liquidation bots on Morpho and examples using Flashbots and Morpho's GraphQL API.

54
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

julien-devatommorpho-rubilmaxshufflewtf0xbulma

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Morpho org migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern going forward. ai
maintainer-change maintainer-added AI (maintainer-change): Morpho org internal restructuring; rubilmax renamed to morpho-rubilmax, consistent with org ownership. ai
maintainer-change maintainer-removed AI (maintainer-change): rubilmax removal is part of same org rename/restructuring, not an external takeover. ai
dependencies unvetted-dep:@paraswap/sdk AI (dependencies): @paraswap/sdk is a well-known DeFi aggregator SDK; stable dependency for this liquidation bot package. ai
dependencies unvetted-peer-dep:evm-maths AI (dependencies): Peer dependency for math utilities; consumer responsibility to vet. ai
dependencies unvetted-dep:@velora-dex/sdk AI (dependencies): DeFi DEX SDK dependency consistent with liquidation bot use case; SLSA-attested publisher. ai
dependencies unvetted-dep:executooor-viem AI (dependencies): Viem executor utility consistent with liquidation SDK purpose; SLSA-attested publisher. ai

Versions (showing 54 of 54)

Version Deps Published
4.0.3 2 / 19
4.0.2 2 / 19
4.0.1 2 / 19
4.0.0 2 / 19
3.0.0 2 / 19
2.22.1 2 / 19
2.22.0 2 / 19
2.21.1 2 / 19
2.21.0 2 / 20
2.20.0 2 / 20
2.19.1 2 / 20
2.19.0 2 / 20
2.18.0 2 / 20
2.17.1 2 / 20
2.17.0 2 / 21
2.16.3 2 / 21
2.16.2 2 / 21
2.16.1 2 / 22
2.16.0 2 / 22
2.15.0 2 / 22
2.14.2 2 / 22
2.14.1 2 / 22
2.14.0 2 / 22
2.13.0 2 / 22
2.12.1 2 / 22
2.12.0 2 / 22
2.11.1 2 / 22
2.11.0 2 / 22
2.10.0 2 / 22
2.9.0 2 / 22
2.8.0 2 / 22
2.7.3 2 / 22
2.7.2 2 / 22
2.7.1 2 / 22
2.7.0 2 / 22
2.6.3 2 / 22
2.6.2 2 / 22
2.6.1 2 / 22
2.6.0 2 / 22
2.5.1 2 / 22
2.5.0 2 / 22
2.4.0 2 / 22
2.3.1 2 / 22
2.3.0 2 / 22
2.2.1 2 / 22
2.2.0 2 / 22
2.1.5 2 / 22
2.1.4 2 / 22
2.1.3 2 / 22
2.1.2 2 / 22
2.1.1 2 / 22
2.1.0 2 / 22
2.0.1 2 / 22
2.0.0 2 / 22

v2.6.1

1 finding
LOW No provenance attestation provenance

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

v2.6.0

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: julien-devatom → rubilmax (on 2025-04-22, known maintainer) provenance

This version was published by a different npm account (rubilmax) than the most recent previously approved version (julien-devatom) on 2025-04-22, but rubilmax 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.5.1

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: julien-devatom → rubilmax (on 2025-04-18, known maintainer) provenance

This version was published by a different npm account (rubilmax) than the most recent previously approved version (julien-devatom) on 2025-04-18, but rubilmax 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.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

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