1.0.133 — diff review from 1.0.132 only (older version)
From google/supply-chain copy of chromium. By Adrian Taylor.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
The current version of serde_json is 1.0.134.
1.0.132 — diff review from 1.0.128 only (older version)
From google/supply-chain copy of chromium. By Liza Burakova.
Methods moved into new deserializer trait in de.rs. New methods for converting Number to i128 or u128 in number.rs No new unsafe changes.
1.0.128 — diff review from 1.0.127 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dana Jansens.
1.0.127 — diff review from 1.0.124 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Lukasz Anforowicz.
1.0.120 — diff review from 1.0.117 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by str4d.
1.0.117 — diff review from 1.0.116 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by Daira Emma Hopwood.
1.0.117 — diff review from 1.0.116 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
build.rs change is to use cargo:rustc-check-cfg to check for features it was
already using.
1.0.116 — diff review from 1.0.110 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
1.0.116 — diff review from 1.0.115 only (older version)
From google/supply-chain copy of chromium. By Dustin J. Mitchell.
No changes that affect safety to run, and no crypto
1.0.114 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.0.108 (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
Reviewed in https://crrev.com/c/5171063
Previously reviewed during security review and the audit is grandparented in.
1.0.99 — diff review from 1.0.97 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
1.0.96 (older version)
From google/supply-chain copy of chromium. Audited without comment by Harshad Phule.
1.0.95 — diff review from 1.0.94 only (older version)
From divviup/libprio-rs. Audited without comment by Brandon Pitman.
1.0.93 — diff review from 1.0.91 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
1.0.92 — diff review from 1.0.91 only (older version)
From divviup/libprio-rs. By Tim Geoghegan.
The only changes are to doccomments, a dev-dependency and the project's CI workflow, so there should be no risk to dependents.
1.0.64 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- does-not-implement-crypto (implies crypto-safe)
-
Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.
Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.
- crypto-safe
Implied by other criteria
All crypto algorithms in this crate have been reviewed by a relevant expert.
Note: If a crate does not implement crypto, use
does-not-implement-crypto, which impliescrypto-safe, but does not require expert review in order to audit for.- unknown
-
May have been packaged automatically without a review
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open serde_json. Alternatively, you can download the tarball of serde_json v1.0.134 or view the source online.
No changes affecting safety-to-run and still no crypto