rustsec
namespacing-rfc
| rustsec | namespacing-rfc | |
|---|---|---|
| 33 | 6 | |
| 1,527 | 47 | |
| 1.4% | - | |
| 9.5 | 3.5 | |
| 2 days ago | 10 months ago | |
| Rust | ||
| GNU General Public License v3.0 or later | - |
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.
rustsec
-
Rust Tooling: 8 tools that will increase your productivity
cargo-audit is a simple Cargo tool for detecting vulnerable Rust crates. You can install it with cargo install cargo-audit, use cargo audit and you’re done! Any vulnerable crates will appear below, like so:
-
Rust Offline?
Further we use cargo-auditable and cargo-audit as part of both our pipeline and regular scanning of all deployed services. This makes our InfoSec and Legal super happy since it means they can also monitor compliance with licenses and patch/update timings.
-
Sudo and Su Being Rewritten in Rust for Memory Safety
Yeah your decade old single header libs get so many audits by comparison.
https://github.com/RustSec/rustsec/tree/main/cargo-audit
https://mozilla.github.io/cargo-vet/
cargo is not npm
-
A CVE has been issued for hyper. Denial of Service possible
PSA: before filing CVEs for other people's projects, file an issue with https://rustsec.org instead
-
Should atomics be unsafe?
Historically, such serious bugs get communicated broadly and addressed very quickly via security advisory blog posts and on https://rustsec.org.
-
Rust from a security perspective, where is it vulnerable?
For known vulnerabilities we have the rustsec vulnerability database. You could have a look over there for inspiration. There's also the related cargo-audit for checking dependencies for known vulnerabilities.
-
capnproto-rust: out-of-bound memory access bug
Would be cool if this was also reported to https://rustsec.org/ that way cargo audit could pick up and alert the users about it.
-
`cargo audit` can now scan compiled binaries
P.S. I also made scanning binaries 5x faster in the latest release of cargo audit.
-
My Rust development workflow (after 3+ years)
Thanks to cargo and the community, project maintenance is straightforward in rust. You'll need to install cargo-outdated and cargo-audit:
-
Mental models for learning Rust
Use the automated tools to assist you in the maintenance of your projects: rustfmt, clippy, cargo update, cargo outdated and cargo-audit.
namespacing-rfc
-
Why so many basic features are not part of the standard library?
An RFC for packages as optional namespaces is still open. An implementation of it exists, but might need an older toolchain to build today.
-
AWS SDK for Rust enters developer preview
There is work going on to allow crate namespacing (foo/bar): https://github.com/Manishearth/namespacing-rfc/blob/main/000...
- How can we make sure this doesn't happen with Crates.io?
-
Crates.io namespaces
A prototype exists for this https://github.com/Manishearth/namespacing-rfc/issues/10
-
Recent crates on docs.rs :(
namespaces have not been ruled out, I have a pre-RFC and there's even a prototype implementation out there
What are some alternatives?
opensnitch - OpenSnitch is a GNU/Linux interactive application firewall inspired by Little Snitch.
wg - Coordination repository for the Secure Code Working Group
vulndb - [mirror] The Go Vulnerability Database
compiler-team - A home for compiler team planning documents, meeting minutes, and other such things.
gosec - Go security checker
libs-team - The home of the library team
crates.io - The Rust package registry
rust-notes - Terse Rust learning material. :crab:
ripasso - A simple password manager written in Rust
rfcs - RFCs for changes to Rust
advisory-db - Security advisory database for Rust crates published through crates.io
ua-parser-js - UAParser.js - Free & open-source JavaScript library to detect user's Browser, Engine, OS, CPU, and Device type/model. Runs either in browser (client-side) or node.js (server-side).