← Home

jsonlint-lines

npm Repository Homepage

Validate JSON

3
Versions
—
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

aaronlidmanansiscamilleannedthompsongretacbianshwardingallsjfirebaughkkaeferlxbarthmapbox-adminmiccolismikemorrismorganherlockermournerrclarkspringmeyertmcwtristenwillwhiteyhahn

Keywords

jsonvalidationlintjsonlint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): The eval() call is in the classic JSON2 polyfill (web/json2.js), a well-known legacy pattern for JSON parsing. It operates on user-supplied JSON text being linted — not attacker-controlled external input in a supply-chain sense. ai
dependencies unvetted-dep:JSV AI (dependencies): JSV (JSON Schema Validator) is a legitimate, long-standing npm package appropriate for a JSON linting tool. No supply-chain risk. ai

Versions (showing 3 of 3)

Version Deps Published
1.7.1 2 / 3
1.7.0 2 / 3
1.6.0 2 / 3

v1.7.1

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.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.