namespacing-rfc
cargo-deny
namespacing-rfc | cargo-deny | |
---|---|---|
6 | 15 | |
47 | 1,559 | |
- | 2.1% | |
3.5 | 8.8 | |
10 months ago | 13 days ago | |
Rust | ||
- | Apache License 2.0 |
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.
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
cargo-deny
-
Please add licenses to your projects, rust DS emulator Dust now dead.
Tip: You can check the licenses of all your dependencies (recursively) using cargo-deny: https://github.com/EmbarkStudios/cargo-deny
- Cargo-deny: a cargo plugin for linting Rust project dependencies
-
What are some useful tools for Rust?
cargo-deny
-
Can versions of a crate be blocked / be made unusable / be made not downloadable?
cargo-deny can help block specified versions of a crate and even has some advisory features that can probably used to block crate with reported vulnerabilities
-
Best way to protect a project from supply chain attacks?
cargo deny for fetching crates only from trusted sources, blacklisting crates, etc.
-
NPM malware and what it could imply for Cargo
Use cargo audit or cargo deny to check the crates in your Cargo.lock to ensure they don't contain any vulnerabilities.
-
This Year in Embedded Rust: 2021 edition
> Explain the crate scanner thing?
I assume a reference to tools that help manage potential issues around dependencies, e.g.:
* https://github.com/rustsec/rustsec/tree/main/cargo-audit
* https://github.com/EmbarkStudios/cargo-deny
"[cargo-audit] Audit Cargo.lock files for crates with security vulnerabilities reported to the RustSec Advisory Database."
"cargo-deny is a cargo plugin that lets you lint your project's dependency graph to ensure all your dependencies conform to your expectations and requirements." e.g. license, security advisories, source.
-
Score card for dependencies in a project
cargo-deny does license and security advisory checking, and cargo-geiger does unsafe checking.
-
How can we make sure this doesn't happen with Crates.io?
cargo-deny
-
Blog post: Cross compiling Rust Windows binaries from Linux
OpenSSL has been banned in our project for a variety of reasons via cargo-deny for around a year and half, it was actually one of the reasons we created it in the first place.
What are some alternatives?
wg - Coordination repository for the Secure Code Working Group
cargo-about - 📜 Cargo plugin to generate list of all licenses for a crate 🦀
compiler-team - A home for compiler team planning documents, meeting minutes, and other such things.
advisory-db - Security advisory database for Rust crates published through crates.io
rustsec - RustSec API & Tooling
xwin - A utility for downloading and packaging the Microsoft CRT headers and libraries, and Windows SDK headers and libraries needed for compiling and linking programs targeting Windows.
libs-team - The home of the library team
crates.io-index - Registry index for crates.io
rust-notes - Terse Rust learning material. :crab:
static_init
rfcs - RFCs for changes to Rust
nextest - A next-generation test runner for Rust.