zod-validation-error
Wrap zod validation errors in user-friendly readable messages
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual (jmike) to GitHub Actions CI/CD publishing with SLSA provenance. Author unchanged, repo unchanged. This is a security improvement. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of dnlytras coincides with move to CI/CD publishing; consistent with team maintenance cleanup, not takeover. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 0 / 19 | |
| 4.0.2 | 0 / 19 | |
| 4.0.1 | 0 / 19 | |
| 4.0.0 | 0 / 19 | |
| 3.5.4 | 0 / 19 | |
| 3.5.3 | 0 / 19 | |
| 3.5.2 | 0 / 19 | |
| 3.5.1 | 0 / 19 | |
| 3.5.0 | 0 / 20 | |
| 3.4.1 | 0 / 20 | |
| 3.4.0 | 0 / 22 | |
| 3.3.1 | 0 / 22 | |
| 3.3.0 | 0 / 22 | |
| 3.2.0 | 0 / 22 | |
| 3.1.0 | 0 / 22 | |
| 3.0.3 | 0 / 22 | |
| 3.0.2 | 0 / 21 | |
| 3.0.1 | 0 / 21 | |
| 3.0.0 | 0 / 21 | |
| 2.1.0 | 0 / 21 | |
| 2.0.0 | 0 / 21 | |
| 1.5.0 | 0 / 21 | |
| 1.4.0 | 0 / 21 | |
| 1.3.1 | 0 / 21 | |
| 1.3.0 | 0 / 21 | |
| 1.2.1 | 0 / 21 | |
| 1.2.0 | 0 / 21 | |
| 1.1.0 | 0 / 21 | |
| 1.0.1 | 0 / 21 | |
| 1.0.0 | 0 / 21 | |
| 0.3.2 | 0 / 21 | |
| 0.3.1 | 0 / 21 | |
| 0.3.0 | 0 / 21 | |
| 0.2.2 | 0 / 21 | |
| 0.2.1 | 1 / 23 | |
| 0.2.0 | 1 / 23 | |
| 0.1.1 | 0 / 23 | |
| 0.1.0 | 0 / 23 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
2 findingsThis version was published by a different npm account than previous versions on 2025-11-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.