Hi HN — I just open-sourced Hibana and hibana-agent.
Hibana is an Affine MultiParty Session Types (MPST) runtime for Rust.
It targets protocol drift in distributed systems. Instead of maintaining separate hand-written state machines in each component, you define interaction once as a global choreography and project role-local behavior at compile time. At runtime, only valid protocol transitions are executable, so invalid moves such as skipping, reusing, or taking the wrong branch are rejected by the protocol model.
The practical value is that one global source of truth replaces multiple hand-written state machines and removes a class of protocol-drift bugs.
Core repo: https://github.com/hibanaworks/hibana
One concrete example is hibana-agent, which demonstrates the same model on an AI agent workflow: allowed action paths are defined in choreography, and only those transitions are executable at runtime.
Example app: https://github.com/hibanaworks/hibana-agent
I built an MCP server that returns the latest versions of the packages you use as dependencies across a variety of ecosystems, like Python, NPM, Go, and GitHub Actions.
It also supports looking up the latest versions of almost 1000 tools, such as development runtimes like Python, Node, dotnet, development tools like Gradle, and various DevOps tools like kubectl or Terraform, via the mise-en-place tool.
Supported ecosystems/tools:
1) Developer ecosystems: NPM, PyPI, NuGet, Maven/Gradle, Go, PHP, Ruby, Rust, Swift, Dart
2) DevOps ecosystems:
- Docker: Docker container images from Docker registries
- Helm: Helm charts from ChartMuseum repositories and OCI registries
- GitHub Actions: Actions hosted on GitHub.com, returning their current version, their inputs and outputs, and (optionally) their entire README with usage examples
- Terraform Providers and Modules: Providers & Modules from Terraform Registry, OpenTofu Registry, or custom registries
- Various tools such as kubectl, terraform, gradle, maven, etc. (as long as they are supported by mise-en-place)
There is a free-for-all hosted version on https://package-version-check-mcp.onrender.com/mcp, and you can run it with Docker or uv (uvx).
This MCP is certainly not the first one to tackle the "outdated dependency" problem. However, I feel that it has various advantages over other MCPs:
- It offers (far) better ecosystem coverage than other MCPs
- There is full test coverage, with automated dependency updates (powered by Renovate) and regular, automated release builds. In contrast, other projects are often vibe-coded, have poor (or no) tests, and are already abandoned
- This MCP uses a minimal Docker/OCI image, hardened for security. SBOMs you generate with tools like Trivy are known to be correct, and the image is signed with Cosign (which allows you to verify its authenticity in case you want to self-host the MCP)
Let me know what you think.
Me and my wife have been meal planning for the last 5 years. We used google keep. It was working for us, but during the years we needed to streamline the process. We tried other methods but nothing worked, so I spent the last 1 month hacking together this custom app. It includes all we needed to make our meal planning at least 5x more efficient. That is: syncing, one tap import of recipes, groceries, shopping mode, weekly meal plan, custom meals (like leftover, veg, eating out..)
We managed to do last Sunday's meal plan in under a minute, since all our favorite (100+) recipes are in one place. We also tagged them by daily food themes ( Monday-pasta, Tuesday- meat..). So we can quickly & mindlessly select a meal for each day.
For the app I used AI to classify groceries by aisle, but not generative, since I found that simple ML Models do a better job.
I would love any feedback from other hackers.
Feel free to use it. It's free, apart from syncing, which I had to add a subscription for due to server costs. I tried to make it generous: one subscription per 10 people.