@zerodev/multi-chain-ecdsa-validator
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@simplewebauthn/browser | AI (phantom-deps): Listed as a runtime dep in package.json; phantom-dep heuristic fires on config-only references, not a real concern for this package. | ai | |
| phantom-deps | phantom-dep:@simplewebauthn/typescript-types | AI (phantom-deps): Type-only dependency; not directly imported at runtime — stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.4.5 | 3 / 0 | |
| 5.4.4 | 3 / 0 | |
| 5.4.3 | 3 / 0 | |
| 5.4.2 | 3 / 0 | |
| 5.4.1 | 3 / 0 | |
| 5.4.0 | 3 / 0 |
v5.4.4
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 (justinzen) than the most recent previously approved version (sahilvasava) on 2025-03-26, but justinzen 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.
v5.4.3
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 (sahilvasava) than the most recent previously approved version (adnpark) on 2025-01-16, but sahilvasava 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.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.