panamax VS rustsec

We had previously tried panamax but it broke constantly. Well, recently we tried again and it worked beautifully this time and we used it to create an offline mirror. It was pretty straightforward to set up, has plenty of customization options, and is quick to update. It includes the Rust toolchain itself as well as the entire ecosystem of https://crates.io/. It's amazing, and it feels like we're online almost! The entire mirror is only about 150GB. Not bad!

I am trying to get a derivation for panamax, a mirror for crates.io, the package registry for Rust libraries.

It looks like panamax is also a program that can be used to mirror a local crates-io registry to ones device. And using .cargo/config one can point to it. https://github.com/panamax-rs/panamax

I’m looking for an equivalent of panamax for rust, for golang. Do you know if a tool like this exists ? The aim is to have a maximum of packages available (ideally all) in an offline environment.

We're no complete strangers to that ;-) (my handle on github is dureuill)

Finally got Panamax's (rust mirror) "serve" command to a point where I've finally made a PR for it!

Work on Panamax (a Rust mirror for rustup and crates.io). It's nearly complete, and as part of building a command to serve a downloaded mirror, I've implemented a warp proof of concept that serves a git repo: https://github.com/panamax-rs/warp-git

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:

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.

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

PSA: before filing CVEs for other people's projects, file an issue with https://rustsec.org instead

Historically, such serious bugs get communicated broadly and addressed very quickly via security advisory blog posts and on https://rustsec.org.

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.

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.

P.S. I also made scanning binaries 5x faster in the latest release of cargo audit.

Thanks to cargo and the community, project maintenance is straightforward in rust. You'll need to install cargo-outdated and cargo-audit:

Use the automated tools to assist you in the maintenance of your projects: rustfmt, clippy, cargo update, cargo outdated and cargo-audit.