@morpho-org/test
Viem-based package that exports utilities to build Vitest & Playwright fixtures that spawn anvil forks as child processes.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; dormancy alone is not a risk signal here. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publish is attested via Sigstore/SLSA from the org's CI; maintainer addition is consistent with org growth, not takeover. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @morpho-org package; 'test' in name is descriptive, not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @morpho-org package; no relation to next.js. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped @morpho-org package; wraps vitest as a peer dep, not a typosquat. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 2.8.2 | 3 / 5 | |
| 2.8.1 | 3 / 5 | |
| 2.8.0 | 3 / 5 | |
| 2.7.3 | 3 / 5 | |
| 2.7.2 | 3 / 5 | |
| 2.7.1 | 3 / 5 | |
| 2.7.0 | 3 / 5 | |
| 2.6.7 | 3 / 5 | |
| 2.6.6 | 4 / 5 | |
| 2.6.5 | 3 / 5 | |
| 2.6.4 | 3 / 5 | |
| 2.6.3 | 3 / 7 | |
| 2.6.2 | 3 / 7 | |
| 2.6.1 | 3 / 7 | |
| 2.6.0 | 3 / 7 | |
| 2.5.0 | 3 / 7 | |
| 2.4.0 | 3 / 7 | |
| 2.3.0 | 3 / 7 | |
| 2.2.0 | 3 / 7 | |
| 2.1.5 | 3 / 7 | |
| 2.1.4 | 3 / 8 | |
| 2.1.3 | 3 / 8 | |
| 2.1.2 | 3 / 8 | |
| 2.1.1 | 3 / 8 | |
| 2.1.0 | 3 / 8 | |
| 2.0.6 | 3 / 8 | |
| 2.0.5 | 3 / 8 | |
| 2.0.4 | 3 / 8 | |
| 2.0.3 | 3 / 8 | |
| 2.0.2 | 3 / 8 | |
| 2.0.1 | 3 / 8 | |
| 2.0.0 | 3 / 8 |
v2.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
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.1.1
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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
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.