eslint-plugin-json-schema-validator
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI with SLSA provenance; this is the documented automated release flow for this package. | ai | |
| dependencies | unvetted-dep:json-schema-migrate-x | AI (dependencies): Direct replacement for json-schema-migrate; scoped rename, no malicious indicators, used by a well-established plugin. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Conditional HTTP module loader pattern; stable and intentional across versions of this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 11 / 0 | |
| 6.1.0 | 11 / 0 | |
| 6.0.3 | 11 / 0 | |
| 6.0.2 | 11 / 0 | |
| 6.0.1 | 11 / 0 | |
| 6.0.0 | 11 / 0 | |
| 5.5.1 | 12 / 0 | |
| 5.5.0 | 12 / 0 | |
| 5.1.0 | 11 / 53 |
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.