0.22.1 — diff review from 0.22.0 only (current)
From divviup/libprio-rs. Audited without comment by David Cook.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.22.1 — diff review from 0.21.3 only (current)
From bytecodealliance/wasmtime. Audited without comment by Andrew Brown.
0.22.1 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
The current version of Base64 is 0.22.1.
0.22.0 — diff review from 0.21.7 only (older version)
From divviup/libprio-rs. Audited without comment by Brandon Pitman.
0.21.7 — diff review from 0.21.5 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
0.21.5 — diff review from 0.21.4 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
0.21.4 — diff review from 0.21.3 only (older version)
From divviup/libprio-rs. Audited without comment by Ameer Ghani.
0.21.1 — diff review from 0.21.0 only (older version)
From divviup/libprio-rs. Audited without comment by Tim Geoghegan.
0.21.0 (older version)
From bytecodealliance/wasmtime. By Pat Hickey.
This crate has no dependencies, no build.rs, and contains no unsafe code.
0.13.1 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.13.1 (older version)
From google/supply-chain copy of chromium. By Adam Langley.
Skimmed the uses of std to ensure that nothing untoward is happening. Code uses forbid(unsafe_code) and, indeed, there are no uses of unsafe
0.13.1 — diff review from 0.13.0 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.13.0 (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…
- 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.- ub-risk-0 (implies ub-risk-1)
-
No unsafe code.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-0
- ub-risk-1 (implies ub-risk-2)
Implied by other criteria
Excellent soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-1
- ub-risk-2 (implies ub-risk-3)
Implied by other criteria
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
- ub-risk-3 (implies ub-risk-4)
Implied by other criteria
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
- ub-risk-4
Implied by other criteria
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- unknown
-
May have been packaged automatically without a review
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of Base64 is 0.22.1.
0.21.7 (older version) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Update from 0.21.5 to 0.21.7
- Documentation updates
- Minor adjustments to the alphabet code
0.21.2 (older version) Thoroughness: Low Understanding: Medium
by kpreid on 2023-05-29
Contains no unsafe code. Contains no IO. Straightforward and well organized code, though the number of different cases and scenarios it handles makes it daunting to thoroughly comprehend. Well commented. Extensive tests.
I have not reviewed the correctness of the algorithms or their resistance to DoS attacks (i.e. whether they can enter infinite loops or over-allocate). I have examined each line to check that it is not obviously malicious or obfuscated.
0.13.0 (older version) Thoroughness: Low Understanding: Medium
Approved without comment by kpcyrd on 2021-11-19
0.5.2 (older version) Thoroughness: None Understanding: None
by dpc on 2019-07-02
-
Issue: High (RUSTSEC-2017-0004)
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock,
are in the crate's repository with a git tag matching the version. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.
To review the actual code of the crate, it's best to use cargo crev open base64. Alternatively, you can download the tarball of base64 v0.22.1 or view the source online.
Packaged for Guix (crates-io)