-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
cargo-supply-chain
Gather author, contributor and publisher data on crates in your dependency graph.
-
nodo
Pre-emptively created repository so the design can be discussed on the issue tracker before commits are made (repo name may change)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
node-ipc
A nodejs module for local and remote Inter Process Communication (IPC), Neural Networking, and able to facilitate machine learning. (by RIAEvangelist)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Use cargo audit or cargo deny to check the crates in your Cargo.lock to ensure they don't contain any vulnerabilities.
Ah wonderful. I had started building something quite like this, where dependencies declared a section in their Cargo.toml's describing their build requirements, and then my program would look those up on crates.io to construct the sandbox.
I have created cargo supply-chain so you could tell how many people you implicitly trust by compiling and running their software.
Use cargo audit or cargo deny to check the crates in your Cargo.lock to ensure they don't contain any vulnerabilities.
If this topic interests you generally, please check out the Rust Secure Code Working Group.
It's using the placeholder name nodo (like "superuser do", but "you no do") and it's currently at https://github.com/ssokolow/nodo
I really wish there was more interest in getting something like Watt upstreamed.
I wonder if using something like cross-rs would help.
I know you said it’s a placeholder, but before you get comfortable and don’t wanna change it lol, n is the name of a popular node version manager.
I experimented a bit with running rust-analyzer under Bubblewrap when using it through NeoVim's LSP integration (see here). Overall it's doable, but it's a tedious process of finding out what needs to write and where, what capabilities you need, etc. I don't see this seeing adoption unless it becomes a first-class feature of the tool in question.
There is a new RFC for this. Please comment and help move it forward if you like it: RFC: Packages as (optional) namespaces