vouch
SES-shim
vouch | SES-shim | |
---|---|---|
10 | 13 | |
17 | 736 | |
- | 0.7% | |
0.0 | 9.9 | |
over 2 years ago | 3 days ago | |
Rust | JavaScript | |
MIT License | 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.
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
SES-shim
-
Malicious libraries can steal all your application secrets in Elixir
I used E in the 90s: http://erights.org/
I haven't kept up with newer systems but I've heard of https://github.com/endojs/endo and just came across http://reports-archive.adm.cs.cmu.edu/anon/home/anon/isr2017... (which says "in the style of the E programming language" -- that's as far as I've read) while looking that up.
WebAssembly was designed to follow the same capability security principles. CHERI too as someone else just brought up.
-
Building an Extension System on the Web
There are other potential solutions I haven’t explored close enough (like Endo and SES), or completely omitted as they’re based on an imperfect blacklist-based approach to security (like sandboxed WebWorkers). However, the mentioned 4 solutions are the top contenders, at least in my mind.
-
Harvesting credit card numbers and passwords from your site
I don't know why you are being silently downvoted, as I think it is worth talking about the potential of using static analysis to improve things.
One promising approach is Endo[0] which "uses LavaMoat to automatically generate reviewable policies that determine what capabilities will be distributed to third party dependencies."
[0] https://github.com/endojs/endo
-
Show HN: Run unsafe user generated JavaScript in the browser
Agoric moved forward and Realms gave way to SES
https://github.com/endojs/endo/tree/master/packages/ses
And Endo is a set of tools (being) built around it to make it more practical for particular usecases
-
Deno 1.26
Yea you could restrict the app by whitelisting only the network services and folders that it will use and that's pretty valuable though at least on Linux could already easily be achieved otherwise. It's good that Deno makes it easy but let's be honest, most people will just pass -A.
I'd love to see a permissions system on a library basis. It would ask the first time a dependency is added and when a new permission is requested after an update. Javascript doesn't make that easy though by being so dynamic. SES could maybe help: https://github.com/endojs/endo/blob/master/packages/ses/READ...
-
Node runtime that sandboxes all NPM dependencies by default
I was poking around on the internet a bit earlier and I found this project. It looks pretty cool, and I figured perhaps a few of y'all might find it cool too!
I have no idea if it actually sandboxes networking by default. This other project, endo[0], seems to add some of that functionality.
Regardless of the maturity though, it makes me excited to see this type of work getting done now!
(What made me want to research it was this[1] thread from the other day.)
0: https://github.com/endojs/endo
1: https://news.ycombinator.com/item?id=30215212
-
Open source maintainer pulls the plug on NPM packages colors and faker, now what
Fortunately the problem could become more tractable if something like SES / Endo takes off:
"Endo protects program integrity both in-process and in distributed systems. SES protects local integrity, defending an application against supply chain attacks: hacks that enter through upgrades to third-party dependencies. Endo does this by encouraging the Principle of Least Authority. ... Endo uses LavaMoat to automatically generate reviewable policies that determine what capabilities will be distributed to third party dependencies."
https://github.com/endojs/endo
- Is metamask running on JavaScript?
- Embedded malware in RC (NPM package)
-
Researcher hacks over 35 tech firms in novel supply chain attack
Yeah. JavaScript is probably the closest to being there (with things like SES[0], LavaMoat[1], etc.) but we're not quite there yet. It's just shocking that this sort of thing is as seemingly obscure as it is; it's like the whole industry has collectively thrown up their hands and said code execution is unavoidably radioactively dangerous. (While simultaneously using package managers that... well.) But it doesn't have to be!
[0] https://github.com/Agoric/ses-shim
[1] https://github.com/LavaMoat/LavaMoat
What are some alternatives?
npm-force-resolutions - Force npm to install a specific transitive dependency version
rfcs - Public change requests/proposals & ideation
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.
Swift Argument Parser - Straightforward, type-safe argument parsing for Swift
gitsign - Keyless Git signing using Sigstore
GHSA-g2q5-5433-rhrf
secimport - eBPF Python runtime sandbox with seccomp (Blocks RCE).
colors.js - get colors in your node.js console
git-ts - Git TimeStamp Utility
sandworm-guard-js - Easy auditing & sandboxing for your JavaScript dependencies 🪱
birdcage - Cross-platform embeddable sandboxing
linux - Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/