@morpho-org/morpho-test
Framework-agnostic extension of `@morpho-org/blue-sdk` that exports test fixtures useful for E2E tests on forks.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 0 / 5 | |
| 4.0.1 | 0 / 5 | |
| 4.0.0 | 0 / 5 | |
| 2.5.0 | 0 / 5 | |
| 2.4.4 | 0 / 5 | |
| 2.4.3 | 0 / 6 | |
| 2.4.2 | 0 / 6 | |
| 2.4.1 | 0 / 6 | |
| 2.4.0 | 0 / 6 | |
| 2.3.0 | 0 / 6 | |
| 2.2.1 | 0 / 6 | |
| 2.2.0 | 0 / 6 | |
| 2.1.0 | 0 / 6 | |
| 2.0.1 | 0 / 6 | |
| 2.0.0 | 0 / 6 |
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.
v2.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.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.