qcell
Statically-checked alternatives to RefCell and RwLock (by uazu)
advisory-db
Security advisory database for Rust crates published through crates.io (by rustsec)
| qcell | advisory-db | |
|---|---|---|
| 2 | 37 | |
| 343 | 866 | |
| - | 3.1% | |
| 4.5 | 9.3 | |
| 9 months ago | 9 days ago | |
| Rust | ||
| Apache License 2.0 | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
qcell
Posts with mentions or reviews of qcell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-23.
-
QCell 0.5.0 release, with no_std support
An unsoundness issue in TCell and TLCell was discovered and fixed by GitHub user steffahn. This is due to Rust TypeId taking into account the lifetime, i.e. you get a different type-id for the same type with different lifetimes, and Rust will automatically cast between them. The solution is to force invariance with some type voodoo. This is a weird corner of Rust I'd never understood before. Ideally std::any::TypeId docs should be improved. (This bug does not affect the safety of correct use of the crate, but fixing it blocks a malicious coder from getting potential unsoundness through a code review.)
-
GhostCell: Separating Permissions from Data in Rust
This is slightly unrelated, but this thread made me dig up my own code that I was writing which was going to be essentially the same as the QCell crate, until I discovered that the QCell crate exists, at which point I stopped working on it and contributed to QCell instead (this PR).
advisory-db
Posts with mentions or reviews of advisory-db.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-26.
- Serde-YAML for Rust has been archived
- When Zig is safer and faster than Rust
-
Advisory: Miscompilation in cortex-m-rt 0.7.1 and 0.7.2
You might also want to add this to https://github.com/rustsec/advisory-db so that cargo audit and Dependabot surface it.
-
"This type of secure-by-default functionality is why we love Go"
The behavior of not extracting outside the specified directory has been the default since forever in Rust's tar. And then it had two RUSTSEC advisories for not handling this correctly in certain corner cases. The latest one in 2021.
-
greater supply chain attack risk due to large dependency trees?
cargo-audit only checks for known issues reported to a vulnerability database.
- capnproto-rust: out-of-bound memory access bug
-
`cargo audit` can now scan compiled binaries
However, I keep getting this error when running cargo audit bin ~/.cargo/bin/*, even if I replace * with a specific binary: Fetching advisory database from `https://github.com/RustSec/advisory-db.git` Loaded 467 security advisories (from C:\Users\jonah\.cargo\advisory-db) Updating crates.io index error: I/O operation failed: The system cannot find the path specified. (os error 3) I'm on Windows 10.
-
MIA Github Assignee on very minor PR
I usually open an issue asking if the crate is still maintained. If there isn't a response for a decent amount of time (like multiple months) and the crate is somewhat popular then it could be worth opening an unmaintained advisory in the advisory-db
-
RustSec Advisory Database Visualization
Here is the visualization of RustSec Advisory Database. I hope it will be helpful. If you need any more charts, feel free to comment.
-
Github Dependency graph adds vulnerability alerting support for Rust
FWIW the RustSec database is still not synced into the Github databse on a regular basis, even though they did an initial import of it. So the cargo audit github action is still relevant.