Compiling in chroot? (for security)

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • nodo

    Pre-emptively created repository so the design can be discussed on the issue tracker before commits are made (repo name may change)

  • (The repo is here if you want to subscribe for notification of updates when I get back to it.)

  • cross

    “Zero setup” cross compilation and “cross testing” of Rust crates

  • Maybe Cross is something to consider? I don't know how much of a sandbox it is, but it runs Cargo inside a Docker container. It has the same CLI as Cargo, you just have to write cross instead of cargo in the terminal.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • crates.io

    The Rust package registry

  • The crates.io people seriously need to just block crate names that are within a tiny string distance of each other. There's no need for "num_cpu" and "num_cpus" to both be valid names. It's been years, and we've seen these problems for years in other package repositories.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts