kernel-wasm
ua-parser-js
| kernel-wasm | ua-parser-js | |
|---|---|---|
| 8 | 29 | |
| 718 | 8,614 | |
| 2.1% | - | |
| 0.0 | 8.4 | |
| about 4 years ago | about 1 month ago | |
| C | JavaScript | |
| GNU General Public License v3.0 only | GNU Affero General Public License v3.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.
kernel-wasm
- Safely run WebAssembly in the Linux kernel, with faster-than-native performance.
- Kernel-WASM: Sandboxed kernel mode WebAssembly runtime for Linux
- Kernel-WASM - Sandboxed kernel mode WebAssembly runtime for Linux
-
Thoughts on improving security of Neovim plugins
WASM is not related to JavaScript in any way, it's just a formal definition (see the spec) for a bytecode and a VM that executes it. One of the problems that WASM tries to solve for web development is to get away from JS because it's such a mess. It's unfortunate that WASM has "Web" in its name, as it's rally not just for Web: there are many embedded runtimes, for example, popular proxy server Envoy supports WASM for writing filters (aka extensions) and there's even WASM runtime for the Linux kernel.
-
Helix: a post-modern text editor
Wasm started in the web, but has since been ported even to the Linux kernel [0]. It seems perfect for situation where you near machine code levels of performance, but don't want to carry different binaries for different CPU architectures - exactly what you want from a plugin system. It also allows far greater isolation than "real" compiled code.
[0] https://github.com/wasmerio/kernel-wasm
ua-parser-js
-
Tell HN: Microsoft Teams is blocking Firefox Nightly
Just look at all the big companies doing it
https://faisalman.github.io/ua-parser-js/
-
Liguard - The Linode Guard
This project is backed under MIT License, special shout out to project UA-Parser, as liguard uses a piece of its source-code.
-
Modern PHP
With NPM, what's actually published is not what's in the git repo, so it's harder to inspect/review vulnerabilities or hijacking. With composer, what's in git _is_ what composer pulls (with the exception of rules in .gitattributes to exclude files etc), making it much easier to trace. One such example: https://github.com/faisalman/ua-parser-js/issues/536
Composer packages are vendor namespaced, so hijacking an abandoned package is not possible (and it is with NPM), some examples like https://www.theregister.com/2021/08/10/github_npm_package/
-
Some developers are fouling up open-source software
Sure, I suppose in theory it could happen with other ecosystems, but for some reason it doesn't. It sure seems to just keep happening in NPM though.
-
Vulnerable and Outdated Components
From the other side, npm package may be hijacked(as it happened recently for ua-parser-js and to other packages earlier). To mitigate that, I don't know, probably, subscribing to some security digest would be the most helpful.
- Red Hat response to Java release cadence change
-
Secure software supply chain: why every link matters
On Oct. 22, 2021, developers of a very common NPM package, ua-parser-js, discovered that some attackers uploaded a compromised version of the package containing malware for Linux and Windows, and were capable of stealing data (at least passwords and cookies from the browser).
-
Thoughts on improving security of Neovim plugins
Since Neovim 0.5 release (which has full Lua support) I see more and more amazing Lua plugins being developed, and I think this trend will likely to continue. But I recently got more concerned about security risks associated with the way Neovim plugins being installed and used (especially after seeing recent compromises like ua-parser-js or coa). Installing typical Neovim plugin is basically downloading and executing random code from the internet on your machine with your user privileges, so hijacked or deliberately malicious plugin could potentially do a lot of damage (like stealing keys/passwords, installing keylogger or just rm -rf / for fun).
-
Hidden XMRig miner malware discovered in hijacked versions of popular ua-parser-js npm library
thread about compromise https://github.com/faisalman/ua-parser-js/issues/536
- Malware Discovered in Popular NPM Package, ua-parser-js
What are some alternatives?
helix - A post-modern modal text editor.
react-device-detect - Detect device, and render view according to detected device type.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
bowser - a browser detector
xi-editor - A modern editor with a backend written in Rust.
remarkable - Markdown parser, done right. Commonmark support, extensions, syntax plugins, high speed - all in one. Gulp and metalsmith plugins available. Used by Facebook, Docusaurus and many others! Use https://github.com/breakdance/breakdance for HTML-to-markdown conversion. Use https://github.com/jonschlinkert/markdown-toc to generate a table of contents.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
enquirer - Stylish, intuitive and user-friendly prompts, for Node.js. Used by eslint, webpack, yarn, pm2, pnpm, RedwoodJS, FactorJS, salesforce, Cypress, Google Lighthouse, Generate, tencent cloudbase, lint-staged, gluegun, hygen, hardhat, AWS Amplify, GitHub Actions Toolkit, @airbnb/nimbus, and many others! Please follow Enquirer's author: https://github.com/jonschlinkert
keys - My personal ergodox, planck layouts.
Serilog - Simple .NET logging with fully-structured events
lspcontainers.nvim - Neovim plugin for lspcontainers.
pnpm - Fast, disk space efficient package manager