wasmex
lowendinsight
| wasmex | lowendinsight | |
|---|---|---|
| - | 1 | |
| 509 | 12 | |
| - | - | |
| 7.7 | 10.0 | |
| 8 days ago | over 1 year ago | |
| Elixir | Elixir | |
| MIT License | BSD 3-clause "New" or "Revised" 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.
wasmex
We haven't tracked posts mentioning wasmex yet.
Tracking mentions began in Dec 2020.
lowendinsight
-
Show HN: LowEndInsight – a “bus-factor” risk analysis tool
What began as a pet-project a few years back, an a start to learning functional programming with Elixir, turned into a bit of a research effort for CS students. I'd asked them what info could they glean from a git repository, specifically about the risks associated with using it (or becoming dependent on it). The focus quickly arrived at "bus factor" - what happens when the main developer moves on. From there we started thinking about other metrics and a couple stood out - mainly the distribution of contributions, and the obvious commit currency time. The initial research was focused on library packages from the main ecosystems - e.g., Javascript's NPM and Python's PyPI. We quickly found that to be a massive challenge - at the time neither required packages to provide a valid URL pointing to their source code. This itself was an indicator of something.
Once the students moved on I continued to think about and would occasionally get asked about the tool. So I picked it back up and slapped an API on it and exposed it via HTTPS POST and GETs.
I am generally looking for feedback. Probably more about the issues associated with dependence on Open Source libraries - the risks derived as software atrophy happens. But what are your ideas about the metainformation that is sitting in a software project's source history.
I've considered doing some ML-y stuff with the commit history, but haven't really found the right things there yet.
Here are some links to the details:
* Library: https://github.com/gtri/lowendinsight
What are some alternatives?
lumen - An alternative BEAM implementation, designed for WebAssembly
lowendinsight-cli - Client for submitting LEI analysis jobs and getting results
explorer - Series (one-dimensional) and dataframes (two-dimensional) for fast and elegant data exploration in Elixir
corsica - Elixir library for dealing with CORS requests. 🏖
lowendinsight-get - LowEndInsight is a simple "bus-factor" risk analysis library for Open Source Software which is managed within a Git repository. This repo is an HTTP-wrapper API around the LowEndInsight Library (https://github.com/gtri/lowendinsight)
rexbug - A thin Elixir wrapper for the redbug Erlang tracing debugger.
redix - Fast, pipelined, resilient Redis driver for Elixir. 🛍
neuron - A GraphQL client for Elixir
extism - The framework for building with WebAssembly (wasm). Easily load wasm modules, move data, call functions, and build extensible apps.
gettext - Internationalization and localization support for Elixir.