paru
cargo-crev
paru | cargo-crev | |
---|---|---|
74 | 55 | |
5,476 | 2,034 | |
- | 1.7% | |
8.8 | 7.7 | |
14 days ago | 29 days ago | |
Rust | Rust | |
GNU General Public License v3.0 only | 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.
paru
- Release Paru v2.0.0 (AUR helper)
-
what do you wish you knew while starting to use arch?
I would also get a AUR helper, I'd recommend paru (don't forget to configure /etc/paru.conf). Just make sure you're checking the validity of AUR packages.
-
Paru not upgrading *-git packages
as the uncommented lines. This has been the default since at least April 2022.
-
Is anyone editing PKGBUILD files locally with paru (local changes without "customizepkg")?
I've just discovered that paru supports adding your own changes to PKGBUILD files if they are committed to the cached git repos and merging them with any upstream upgrades:
-
Discovery gives "The PackageKit daemon has crashed" error suddenly (Arch)
If you use AUR packages, you might want to use an AUR helper that wraps pacman, like paru or yay.
-
Concerns Over Arch Stability
paru is an AUR Helper, which also will perform pacman actions (install, upgrade, removal, etc)
-
It’s JavaScript all the way down
maybe check out paru - it throws up the PKGBUILD whenever you’re installing a package (or upgrading one when it’s changed)
-
Is there any software helps build AUR packages and update them?
paru: https://github.com/Morganamilo/paru
-
Need help installing webcam drivers ipu6
Thanks. Installing intel-ipu6-dkms-git from AUR using paru is giving error, says
- Is there a way to apply a patch to an AUR package on the fly, without editing the PKGBUILD?
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?
yay - Yet another Yogurt - An AUR Helper written in Go
crates.io - The Rust package registry
octopi - A powerful Pacman (Package Manager) front end using Qt libs
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
aur - A secure, multilingual package manager for Arch Linux and the AUR.
crates.io-index - Registry index for crates.io
rua - Build tool for Arch Linux providing control, review and jailed build options
serde - Serialization framework for Rust
ArchWSL - ArchLinux based WSL Distribution. Supports multiple install.
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
topgrade - Upgrade everything
Rustup - The Rust toolchain installer