These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
1.0.3 (current) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Review update from 0.1.11 (yanked) to 1.0.3
- Added forbid(unsafe_code)
- Updates related to avr and msp430 targets
The current version of atomic-polyfill is 1.0.3.
0.1.5 (older version) Thoroughness: Low Understanding: Medium
Approved without comment by kornelski on 2021-12-06
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.0.3 — diff review from 0.1.11 only (current)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
The current version of atomic-polyfill is 1.0.3.
1.0.2 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package atomic-polyfill 1.0.2 from crates.io using debcargo 2.6.0
[ Sylvestre Ledru ]
- Package atomic-polyfill 0.1.5 from crates.io using debcargo 2.5.0
1.0.1 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.1.11 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
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.- unknown
-
May have been packaged automatically without a review
Lib.rs has been able to verify that all files in the crate's tarball 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 atomic-polyfill
. Alternatively, you can download the tarball of atomic-polyfill v1.0.3 or view the source online.
The author has archived the GitHub repository and mentions deprecation in project's README.
Possible alternatives