deno_install
LavaMoat
deno_install | LavaMoat | |
---|---|---|
9 | 16 | |
948 | 819 | |
-0.2% | 2.1% | |
4.9 | 9.8 | |
18 days ago | 2 days ago | |
PowerShell | JavaScript | |
- | 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.
deno_install
-
API using Deno and ElyasiaJS
import { App, Router } from "https://deno.land/x/[email protected]/mod.ts"; const app = new App(); const router = new Router(); // Define your API routes router.get("/hello", (ctx) => { ctx.response.body = "Hello, World!"; }); app.use(router.routes()); app.use(router.allowedMethods()); // Start the server app.listen({ port: 8000 }); console.log("Server is running on http://localhost:8000");
-
What's Your Favorite Tech Stack and Why?
Deno: Deno with one of it's frameworks (like Fresh
-
Avoid conflicts between denols and tsserver in Neovim
lspconfig.denols.setup({ root_dir = lspconfig.util.root_pattern("deno.json", "deno.jsonc"), init_options = { lint = true, unstable = true, suggest = { imports = { hosts = { ["https://deno.land"] = true, ["https://cdn.nest.land"] = true, ["https://crux.land"] = true, }, }, }, }, on_attach = on_attach, })
- how do you uninstall deno
-
Deno.js in Production. Key Takeaways.
https://deno.land/install.sh is a redirect to https://deno.land/x/install.sh, which is treated as any /x/ (community) module. These modules are immutable clones of github tags (in this case, https://github.com/denoland/deno_install/). If someone would manage to breach the AWS S3 buckets that we use for module storage, it wouldn't be just a problem for installation of the deno CLI, but a problem for any module on the registry.
-
Get started with deno (from NodeJS or not...)
In any case, Deno ships a lot more things but this is enough to get us started. Any additional information can be found on the official repository url that I will be linking at the end of the article. As for a little start, since nodejs has been used as a very popular web server, I thought it might be interesting to start building a deno version of it. To start off, let's install deno. Depending on your OS you might want to refer to Install Docs
-
a first look at oak
You can find a list of different installation methods on the official deno.land documentation and the deno_install repo.
-
Serverless API with Deno and Begin - Part 1
You can install Deno in a few different ways. I chose to install it with brew install deno, but you can check their docs for other methods.
-
deno is the future?
See deno_install and releases for other options.
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