0.25.3 (current)
From google/supply-chain copy of chromium. By Dominik Röttsches.
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 read-fonts is 0.25.3.
0.22.1 — diff review from 0.22.0 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Lukasz Anforowicz.
0.19.3 — diff review from 0.19.2 only (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
No unsafe.
0.19.1 — diff review from 0.19.0 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dana Jansens.
0.15.6 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Taylor Cramer.
Reviewed in CL 611302616
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- safe-to-run
Implied by other criteria
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)
-
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
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 read-fonts. Alternatively, you can download the tarball of read-fonts v0.25.3 or view the source online.
Fixes for hdmx processing (use explicit record size), overflow fixes for packed point numbers. Fixes for midpoint computation, and follow-up fix to reinstate FreeType equivalence. Feature gating experimential spec features.