← Home

@redocly/ajv

npm Repository Homepage

Another JSON Schema Validator

11
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

romanhotsiyalawaradamaltmanmarshevskyyvolodymyr-rutskyislavikbezkorovainyi

Keywords

JSONschemavalidatorvalidationjsonschemajson-schemajson-schema-validatorjson-schema-validation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance slsa-provenance AI (provenance): Package publishes via GitHub Actions with SLSA provenance; this is the expected CI/CD pipeline for Redocly packages. ai
provenance publisher-changed AI (provenance): Publisher is now GitHub Actions with SLSA provenance attestation — this is a CI/CD pipeline publishing on behalf of Redocly, a stronger integrity signal than a personal account. ai
semgrep semgrep:new-function-constructor AI (semgrep): AJV's core design compiles JSON Schema validators via new Function(). Input is internally generated code, not user-supplied strings. This is a stable, intentional pattern for this package. ai

Versions (showing 11 of 11)

Version Deps Published
8.18.3 4 / 41
8.18.2 4 / 41
8.18.1 4 / 41
8.18.0 4 / 41
8.17.4 4 / 41
8.17.3 4 / 41
8.17.2 4 / 41
8.17.1 4 / 41
8.11.4 4 / 41
8.11.3 4 / 41
8.11.2 4 / 41

v8.18.2

2 findings
HIGH Publisher changed: romanhotsiy → GitHub Actions (on 2026-04-06) provenance

This version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v8.18.1

2 findings
HIGH Publisher changed: romanhotsiy → GitHub Actions (on 2026-03-26) provenance

This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v8.11.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.11.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.