← Home

@redocly/ajv

npm Repository Homepage

Another JSON Schema Validator

19
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 19 of 19)

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
8.11.1 4 / 41
8.11.0 4 / 41
8.6.5 4 / 39
8.6.4 4 / 39
8.6.3 4 / 39
8.6.2 4 / 39
8.6.1 4 / 39
8.6.0 4 / 39

v8.11.1

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.

v8.11.0

1 finding
LOW No provenance attestation provenance

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

v8.6.5

1 finding
LOW No provenance attestation provenance

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

v8.6.4

1 finding
LOW No provenance attestation provenance

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

v8.6.3

1 finding
LOW No provenance attestation provenance

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

v8.6.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: romanhotsiy → andriyleliv (on 2021-06-30, known maintainer) provenance

This version was published by a different npm account (andriyleliv) than the most recent previously approved version (romanhotsiy) on 2021-06-30, but andriyleliv 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.

v8.6.1

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.

v8.6.0

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.