ajv-formats
Format validation for Ajv v7+
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
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): Dormancy followed by major version bump is consistent with planned release by new maintainer in ajv-validator org. | ai | |
| provenance | publisher-changed | AI (provenance): jason-green is a known collaborator in the ajv-validator org; legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jason-green added as maintainer as part of legitimate ajv-validator org transition. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 1 / 15 | |
| 3.0.0 | 1 / 15 | |
| 2.1.1 | 1 / 15 | |
| 2.1.0 | 1 / 15 | |
| 2.0.2 | 1 / 15 | |
| 2.0.1 | 0 / 15 | |
| 2.0.0 | 0 / 15 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-03-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.