@morpho-org/liquidity-sdk-viem
Viem-based package that helps seamlessly calculate the liquidity available through the PublicAllocator.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 0 / 17 | |
| 4.0.2 | 0 / 17 | |
| 4.0.1 | 0 / 17 | |
| 4.0.0 | 0 / 17 | |
| 3.0.2 | 0 / 17 | |
| 3.0.1 | 0 / 17 | |
| 3.0.0 | 0 / 16 | |
| 2.0.1 | 0 / 16 | |
| 2.0.0 | 0 / 16 | |
| 1.4.1 | 0 / 16 | |
| 1.4.0 | 0 / 16 | |
| 1.3.7 | 0 / 16 | |
| 1.3.6 | 0 / 17 | |
| 1.3.5 | 0 / 17 | |
| 1.3.4 | 0 / 18 | |
| 1.3.3 | 0 / 18 | |
| 1.3.2 | 0 / 18 | |
| 1.3.1 | 0 / 18 | |
| 1.3.0 | 0 / 18 | |
| 1.2.1 | 0 / 18 | |
| 1.2.0 | 0 / 18 | |
| 1.1.0 | 0 / 18 | |
| 1.0.1 | 0 / 18 | |
| 1.0.0 | 0 / 18 |
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.