smimesign
vouch
| smimesign | vouch | |
|---|---|---|
| 2 | 10 | |
| 569 | 17 | |
| 0.5% | - | |
| 0.0 | 0.0 | |
| about 1 month ago | over 2 years ago | |
| Go | Rust | |
| MIT License | 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.
smimesign
-
Signing Git Commits with Your SSH Key
I believe GitHub's smimesign can use RFC3161 timestamps:
How to specify a timestamp server
https://github.com/github/smimesign/issues/47
-
Gitsign
smimesign supports timestamping with a normal timestamp server, with a bit of extra effort. It would be cool if your tool could (at least optionally) do the same.
https://github.com/github/smimesign/issues/47#issuecomment-4...
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?
gitsign - Keyless Git signing using Sigstore
npm-force-resolutions - Force npm to install a specific transitive dependency version
git-ts - Git TimeStamp Utility
platform-samples - A public place for all platform sample projects.
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.
community - Public feedback discussions for: GitHub Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more!
secimport - eBPF Python runtime sandbox with seccomp (Blocks RCE).
cargo-vet - supply-chain security for Rust
SES-shim - Endo is a distributed secure JavaScript sandbox, based on SES
opentimestamps-client - OpenTimestamps client
birdcage - Cross-platform embeddable sandboxing