dotfiles
cargo-crev
dotfiles | cargo-crev | |
---|---|---|
12 | 55 | |
- | 2,034 | |
- | 1.7% | |
- | 7.7 | |
- | about 1 month 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.
dotfiles
-
Silverblue container users: what does your environment look like?
Oh you'd still use a Git repository (e.g. like I do here), stow just takes care of creating the necessary symbolic links (and skipping those that already exist).
-
NPM malware and what it could imply for Cargo
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.
-
Systemd service sandboxing and security hardening 101
You can also use Bubblewrap, but getting it up and running requires a lot more fiddling around. For example, this is what I use to isolate Zoom from the rest of my system: https://gitlab.com/yorickpeterse/dotfiles/-/blob/0a0492c78b6...
In my case I'm using Bubblewrap because Firejail was only used for Zoom, and this felt a bit of a waste considering Bubblewrap was already installed.
-
What do you use the tabline for?
This is implemented using some custom Lua code.
- Lists of lua-based nvim config files?
-
Is there a way to set abbreviations through lua?
There's no first-class API for this. I use this setup. This is OK, though I only have two abbreviations, and it does feel a bit overkill for just that.
-
When using the terminal emulator and opening a file within a terminal emulator, open it instead in a new buffer.
I've been using neovim-remote for quite some time, and it works perfectly fine. Here is what I use to open NeoVim as usual outside of an existing NeoVim session, and inside the existing session whenever I run nvim from NeoVim's terminal emulator.
-
neovim lsp - how do you get diagnostic mesages to show at the bottom instead of in-line?
You can use this code I wrote for that. You then hook it up like this.
-
Which one would you rather use for completion?
Adjust the icons LSP uses for various symbol types like this. If you leave this out, you need to adjust these lines to use the correct text/icons instead.
-
Neovim 0.5 Is Overpowering
The documentation is there, but it's a bit lacking/confusing here and there. It's also mostly foundational work, and you still need to cobble things together (either manually or using a plugin).
With that said, you can build things quite nicely with it. For example, I have a custom linter setup, custom loclist/quickfix list formatting and populating from LSP data, and a bunch of other things; all using the foundational work coming in NeoVim 0.5.
If anybody is curious, you can find my NeoVim configuration here: https://gitlab.com/yorickpeterse/dotfiles/-/tree/master/dotf...
p.s. In case anybody wonders "why Lua?", for me this mostly comes down to this: I hate Lua, but I hate Vimscript even more.
cargo-crev
-
Hard disk LEDs and noisy machines
In other cases it may be more documented, such as Golangs baked-in telemetry.
There should be better ways to check these problems. The best I have found so far is Crev https://github.com/crev-dev/crev/. It's most used implementation is Cargo-crev https://github.com/crev-dev/cargo-crev, but hopefully it will become more required to use these types of tools. Certainty and metrics about how many eyes have been on a particular script, and what expertise they have would be a huge win for software.
-
Rust Without Crates.io
The main problem the author is talking about is actually about version updates, which in Maven as well as crates.io is up to each lib's author, and is not curated in any way.
There's no technical solution to that, really. Do you think Nexus Firewall can pick up every exploit, or even most? How confident of that are you, and what data do you have to back that up? I don't have any myself, but would not be surprised at all if "hackers" can easily work around their scanning.
However, I don't have a better approach than using scanning tools like Nexus, or as the author proposes, use a curated library repository like Debian is doing (which hopefully gets enough eyeballs to remain secure) or the https://github.com/crev-dev/cargo-crev project (manually reviewed code) also mentioned. It's interesting that they mention C/C++ just rely on distros providing dynamic libs instead which means you don't even control your dependencies versions, some distro does (how reliable is the distro?)... I wonder if that could work for other languages or if it's just as painful as it looks in the C world.
-
I don't care about cookies” extension bought by Avast, users jump ship
For instance, the worst company imaginable may be in charge of software that was once FOSS, and they may change absolutely nothing about it, so it should be fine. However, if a small update is added that does something bad, you should know about it immediately.
The solution seems to be much more clearly in the realm of things like crev: https://github.com/crev-dev/cargo-crev/
Wherein users can get a clear picture of what dependencies are used in the full chain, and how they have been independently reviewed for security and privacy. That's the real solution for the future. A quick score that is available upon display everytime you upgrade, with large warnings for anything above a certain threshold.
-
I think there should be some type of crates vertification especially the popular ones?
The metrics on crates.io are a useful sniff test, but ultimately you need to review things yourself, or trust some contributors and reviewers. Some projects, like cargo crev or cargo vet can help with the process.
-
[Discussion] What crates would you like to see?
You can use cargo-geiger or cargo-crev to check for whether people you trusted (e.g. u/jonhoo ) trust this crate.
-
Pip and cargo are not the same
There is a similar idea being explored with https://github.com/crev-dev/cargo-crev - you trust a reviewer who reviews crates for trustworthiness, as well as other reviewers.
- greater supply chain attack risk due to large dependency trees?
-
Why so many basic features are not part of the standard library?
[cargo-crev](https://github.com/crev-dev/cargo-crev) looks like a good step in the right direction but not really commonly used.
-
“You meant to install ripgrep”
'cargo crev' makes this kind of workflow possible: https://github.com/crev-dev/cargo-crev
-
Difference between cargo-vet and cargo-crev?
The crev folks themselves are no fans of PGP but need a way to security identify that you are in fact the review author, so that's where the id generation comes in. Ultimately crev is just a bunch of repos with text files you sign with IDs. The nice property is that you can chain these together into a web of trust and it's unfortunate that vet doesn't just use the same signed files on repos model as a foundation because even if they don't trust anyone else, we could turn around and trust them.
What are some alternatives?
nvim-autopairs - autopairs for neovim written in lua
crates.io - The Rust package registry
NeoVim-config - My neovim config written in Lua!
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
crates.io-index - Registry index for crates.io
asyncomplete.vim - async completion in pure vim script for vim8 and neovim
serde - Serialization framework for Rust
config_manager - My configuration files and tools
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
vim-vsnip - Snippet plugin for vim/nvim that supports LSP/VSCode's snippet format.
Rustup - The Rust toolchain installer