jsonata
JSON query and transformation language
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): Transition to GitHub Actions CI/CD publishing with SLSA attestation; stable for this package. | ai | |
| source-diff | net-exec-file:jsonata-es5.js | AI (source-diff): jsonata-es5.js is a Browserify UMD bundle of the library transpiled via Babel; standard browser bundle patterns trigger the rule but pose no risk. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.2.2 | 0 / 17 | |
| 2.2.1 | 0 / 17 | |
| 2.2.0 | 0 / 17 | |
| 1.8.7 | 0 / 17 | |
| 1.3.3 | 0 / 16 | |
| 1.3.2 | 0 / 16 | |
| 1.3.1 | 0 / 16 | |
| 1.3.0 | 0 / 16 | |
| 1.2.6 | 0 / 16 | |
| 1.2.5 | 0 / 16 | |
| 1.2.4 | 0 / 16 | |
| 1.2.3 | 0 / 16 | |
| 1.2.2 | 0 / 16 | |
| 1.2.1 | 0 / 16 | |
| 1.2.0 | 0 / 11 | |
| 1.1.1 | 0 / 9 | |
| 1.1.0 | 0 / 9 | |
| 1.0.10 | 0 / 8 | |
| 1.0.9 | 0 / 8 | |
| 1.0.8 | 0 / 8 | |
| 1.0.7 | 0 / 8 | |
| 1.0.6 | 0 / 8 | |
| 1.0.5 | 0 / 8 | |
| 1.0.4 | 0 / 8 | |
| 1.0.3 | 0 / 6 | |
| 1.0.2 | 0 / 8 | |
| 1.0.1 | 0 / 8 | |
| 1.0.0 | 0 / 8 |
v2.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (jsonata) on 2026-05-14, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.