← Home

is-my-json-valid

npm Repository Homepage

A [JSONSchema](https://json-schema.org/) validator that uses code generation to be extremely fast.

11
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

freealllinusumafintoshyoshuawuytsemilbaywatsonemilbayes

Keywords

jsonschemaorderlyjsonschema

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): mafintosh is the repository owner (mafintosh/is-my-json-valid) and a highly trusted publisher; the 2020 transfer to mafintosh is a legitimate maintainer transition, not a compromise. ai

Versions (showing 11 of 11)

Version Deps Published
2.20.6 5 / 3
2.20.5 5 / 3
2.20.4 5 / 3
2.20.3 5 / 3
2.20.2 5 / 3
2.20.1 5 / 3
2.20.0 5 / 3
2.19.0 5 / 3
2.18.0 5 / 3
2.17.2 5 / 2
0.0.0 3 / 1

v2.20.6

1 finding
LOW No provenance attestation provenance

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

v2.20.5

1 finding
LOW No provenance attestation provenance

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

v2.20.4

2 findings
HIGH Publisher changed: mafintosh → linusu (on 2020-06-29) provenance

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

LOW No provenance attestation provenance

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

v2.20.3

1 finding
LOW No provenance attestation provenance

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

v2.20.2

1 finding
LOW No provenance attestation provenance

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

v2.20.1

2 findings
HIGH Publisher changed: linusu → mafintosh (on 2020-06-26) provenance

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

LOW No provenance attestation provenance

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

v2.20.0

1 finding
LOW No provenance attestation provenance

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

v2.19.0

1 finding
LOW No provenance attestation provenance

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

v2.18.0

1 finding
LOW No provenance attestation provenance

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

v2.17.2

1 finding
LOW No provenance attestation provenance

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