0.5.3 (current)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.5.3 (current)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar, Augie Fackler.
0.5.3 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
The current version of BitSet is 0.5.3.
0.5.2 (older version)
From mozilla/supply-chain copy of hg. By Aria Beingessner.
Another crate I own via contain-rs that is ancient and maintenance mode, no known issues.
0.5.2 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Packaged for Debian (stable). Changelog:
- Team upload.
- Package bit-set 0.5.2 from crates.io using debcargo 2.5.0
- Relax dev-dependency on rand.
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
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- ub-risk-2 (implies ub-risk-3)
-
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
- 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 bit-set. Alternatively, you can download the tarball of bit-set v0.5.3 or view the source online.
Reviewed in CL 615008047 Uses unsafe operations from bit-vec that are not actually unsafe.