cargo-vet
vouch
cargo-vet | vouch | |
---|---|---|
12 | 10 | |
598 | 17 | |
5.7% | - | |
7.6 | 0.0 | |
about 1 month ago | over 2 years ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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.
cargo-vet
-
Ferrocene – Rust for Critical Systems
For supply chain security, you might be interested in cargo-vet[0], a tool for coordinating and requiring manual reviews of open source dependencies. Both Mozilla and Google[1] have started publishing their audits.toml files, which are a machine-readable file describing what source code reviews they have performed.
[0] https://github.com/mozilla/cargo-vet
[1] https://opensource.googleblog.com/2023/05/open-sourcing-our-...
-
Rust security scanning options
there is also cargo-vet for manual auditing of the source code of the crates, which is not something that can be done automatically. Quite a few companies and orgs use it now like Mozilla, Google, Bytecode Alliance, us (Embark Studios), ISRG, zcash etc. And believe its usage will expand significantly going forward with corporate users and security sensitive projects/orgs.
-
NPM repository flooded with 15,000 phishing packages
If you don't know the author, signatures do nothing. Anybody can sign their package with some key. Even if you could check the author's identity, that still does very little for you, unless you know them personally.
It makes a lot more sense to use cryptography to verify that releases are not malicious directly. Tools like crev [1], vouch [2], and cargo-vet [3] allow you to trust your colleagues or specific people to review packages before you install them. That way you don't have to trust their authors or package repositories at all.
That seems like a much more viable path forward than expecting package repositories to audit packages or trying to assign trust onto random developers.
[1]: https://github.com/crev-dev/crev [2]: https://github.com/vouch-dev/vouch [3]: https://github.com/mozilla/cargo-vet
-
How do regulates companies handle software of unknown Provence (SOUP) when using needed open source crates?
The other approach is https://github.com/mozilla/cargo-vet
- greater supply chain attack risk due to large dependency trees?
- Dozens of malicious PyPI packages discovered targeting developers
-
Best way to protect a project from supply chain attacks?
cargo crev and cargo vet for reviewing dependencies and using reviewed versions
-
Vetting the Cargo
Since the audits are designed to be used at a per project level and contributed directly into the VCS repo (allowing you to using git signing for example) I don't quite understand what additional off-line cryptographic signatures are required here (considering that Cargo's lockfiles already contain a hash of the crate which would prevent the project from getting an altered version of a crate accidentally and that SHA validation is being considered as part of vet as well https://github.com/mozilla/cargo-vet/issues/116).
- Mozilla/cargo-vet – supply-chain security for Rust
- Gitsign
vouch
-
NPM repository flooded with 15,000 phishing packages
If you don't know the author, signatures do nothing. Anybody can sign their package with some key. Even if you could check the author's identity, that still does very little for you, unless you know them personally.
It makes a lot more sense to use cryptography to verify that releases are not malicious directly. Tools like crev [1], vouch [2], and cargo-vet [3] allow you to trust your colleagues or specific people to review packages before you install them. That way you don't have to trust their authors or package repositories at all.
That seems like a much more viable path forward than expecting package repositories to audit packages or trying to assign trust onto random developers.
[1]: https://github.com/crev-dev/crev [2]: https://github.com/vouch-dev/vouch [3]: https://github.com/mozilla/cargo-vet
- Dozens of malicious PyPI packages discovered targeting developers
-
Vetting the Cargo
Alternatives to cargo-vet that has been mentioned before here on HN:
- https://github.com/crev-dev/crev
- https://github.com/vouch-dev/vouch
Anyone know of any more alternatives or similar tools already available?
- Vouch – A multi-ecosystem package code review system
- Gitsign
-
Embedded malware in RC (NPM package)
I've created Vouch in an attempt to address this problem:
https://github.com/vouch-dev/vouch
Vouch lets users create and share reviews for NPM packages. Project dependencies can then be checked against those reviews.
Vouch uses extensions to interface with package ecosystems. It's simple to create a new extension. Extensions currently exist for NPM, PyPi, and Ansible Galaxy.
I'm currently working on a website to index known reviews and publish official reviews.
I hope you guys find it useful! Drop by the Matrix channel if you have any feedback to share: #vouch:matrix.org
- Vouch: A dependency review tool for NPM packages
- BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
- Vouch: A dependency review tool for PyPI packages
What are some alternatives?
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
npm-force-resolutions - Force npm to install a specific transitive dependency version
W4SP-Stealer - w4sp Stealer official source code, one of the best python stealer on the web [GET https://api.github.com/repos/loTus04/W4SP-Stealer: 403 - Repository access blocked]
is-number - JavaScript/Node.js utility. Returns `true` if the value is a number or string number. Useful for checking regex match results, user input, parsed strings, etc.
git-ts - Git TimeStamp Utility
gitsign - Keyless Git signing using Sigstore
secimport - eBPF Python runtime sandbox with seccomp (Blocks RCE).
security-wg - Node.js Ecosystem Security Working Group
SES-shim - Endo is a distributed secure JavaScript sandbox, based on SES