LavaMoat
tldr
LavaMoat | tldr | |
---|---|---|
16 | 262 | |
824 | 48,760 | |
2.7% | 1.3% | |
9.8 | 10.0 | |
1 day ago | about 6 hours ago | |
JavaScript | Markdown | |
MIT License | GNU General Public License v3.0 or later |
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.
LavaMoat
-
Ledger's NPM account has been hacked
Just yesterday I watched a talk [0] at WarsawJS about LavaMoat [1], a set of tools to protect against malicious behaviour from npm dependencies. Guess itโs time to look into it deeper.
[0]: https://naugtur.pl/pres3/lava/2023end.html
[1]: https://github.com/LavaMoat/LavaMoat
-
Dozens of malicious PyPI packages discovered targeting developers
You are basically talking about Lavamoat. It provides tooling and policies for SES, which aims to make it into standards.
https://github.com/LavaMoat/LavaMoat
-
Supply chain security - prevent, not avoid
Enter: lavamoat. https://github.com/LavaMoat/LavaMoat
- LavaMoat: Tools for sandboxing your dependency graph
-
Deno.js in Production. Key Takeaways.
You should check out Lavamoat: https://github.com/LavaMoat/LavaMoat
It attempts to do what you're essentially describing. It was built by the MetaMask team, where supply chain attacks are an obviously huge risk.
I've spent some time trying to get it working in an app, but haven't been able to get it all the way working. It's still pretty beta and not well documented.
- Node.js packages don't deserve your trust
-
How to respond to growing supply chain security risks?
And it is happening right now. Github is opening the GitHub Advisory Database to community submissions. Awesome community NodeSecure builds cool things like scanner and js-x-ray. There are also lockfile-lint, LavaMoat, Jfrog-npm-tools (and I am sure there is more).
- On node-ipc and the importance of trusting trust
-
NPM package compromised by author: erases files on RU / BY computers on install
There is a proposal to add OCAPs on a language level in TC39[0]. There is already a drop-in implementation which already works in both Nodejs and browsers[1].
As a developer who wants to sandbox your own (recursive) dependencies, this is made accessible today in Lavamoat[2]. Basically a package or app can provide a policy manifest specifying which capabilities (e.g. network or filesystem access) should be granted for each dependency. Also comes with a tool that will auto-generate a starting point from your existing dependency tree.
IMO this is the future. Currently it does come with a performance penalty but hopefully this idea will catch on and make it into runtime implementations.
Lavamoat is still marked as "preprod" on npm but talking to the author it's a matter of days or weeks until the first stable release.
[0]: https://news.ycombinator.com/item?id=30703817
[1]: https://github.com/endojs/endo/tree/master/packages/ses
[2]: https://github.com/LavaMoat/LavaMoat
- Node runtime that sandboxes all NPM dependencies by default
tldr
-
Ask HN: Is there a GUI for bash shell?
Maybe this already helps: https://github.com/tldr-pages/tldr
-
Try / Ripgrep in Y Minutes
A bit of an aside, but I really like "guides to things we otherwise take for granted". So few man pages are built around example use cases, but those are often what make the case for a tool!
A similar spirit to projects like https://github.com/tldr-pages/tldr/ , but this has a lot more useful detail.
The ripgrep author has a blog post on performance and benchmarking that is an interesting read in itself: https://blog.burntsushi.net/ripgrep/
- Serving my blog posts as Linux manual pages
- Tldr: Simplified and community-driven man pages
- Tell HN: My Favorite Tools
-
Should you add screenshots to documentation?
Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat
-
Have i made my own linux distro? ^_^
a very excellent tool to grab is TLDR https://tldr.sh/
- fixedIt
-
Day 2 - Basic navigation
And that's why tldr is such a powerful tool! You can easily install it with sudo apt install tldr or follow this demo.
- Tldr Pages
What are some alternatives?
metamask-extension - :globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites
cheat - cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.
create-vue - ๐ ๏ธ The recommended way to start a Vite-powered Vue project
tealdeer - A very fast implementation of tldr in Rust.
vue-cli - ๐ ๏ธ webpack-based tooling for Vue.js Development
cheat.sh - the only cheat sheet you need
cli - the package manager for JavaScript
zsh-autosuggestions - Fish-like autosuggestions for zsh
handlebars-helpers - 188 handlebars helpers in ~20 categories. Can be used with Assemble, Ghost, YUI, express.js etc.
navi - An interactive cheatsheet tool for the command-line
EventSource - a polyfill for http://www.w3.org/TR/eventsource/
fish-shell - The user-friendly command line shell.