Show HN: Onus – self-hostable vuln scanner combining 8 tools into one report https://ift.tt/FR19y8H

Show HN: Onus – self-hostable vuln scanner combining 8 tools into one report https://ift.tt/3mL7kr9 July 22, 2026 at 10:24PM

Show HN: Edky, a CLI to convert Ed25519 public keys from one encoding to another https://ift.tt/7TVLscf

Show HN: Edky, a CLI to convert Ed25519 public keys from one encoding to another Everything increasingly runs on Ed25519 keypairs, but Ed25519 public keys can be encoded as text in dozens of surface-incompatible different ways: hexadecimal, Base64 (OpenSSH), Base32z (iroh, pkdns), Base58 (NEAR), and Multibase (IPFS, libp2p), just for starters. Edky is a command-line tool and Rust library that converts between these Ed25519 surface encodings, aiding use of the same underlying keypair across e.g. an iroh endpoint, a libp2p peer, or a NEAR Protocol account. (Surprisingly, a conversion utility like this didn't yet exist!) $ cargo binstall -y edky $ edky convert -f iroh -t libp2p 47pjoycnsrfmxikm95jh13y88e8qnhzu5kungjpxyepgt7a8krpy z6MktwupdmLXVVqTzCw4i46r4uGyosGXRnR3XjN4Zq7oMMsw $ edky convert -f libp2p -t iroh z6MktwupdmLXVVqTzCw4i46r4uGyosGXRnR3XjN4Zq7oMMsw 47pjoycnsrfmxikm95jh13y88e8qnhzu5kungjpxyepgt7a8krpy $ edky convert -f near -t hex ed25519:FVen3X669xLzsi6N2V91DoiyzHzg1uAgqiT8jZ9nS96Z d75a980182b10ab7d54bfed3c964073a0ee172f3daa62325af021a68f707511a $ edky convert -f hex -t near d75a980182b10ab7d54bfed3c964073a0ee172f3daa62325af021a68f707511a ed25519:FVen3X669xLzsi6N2V91DoiyzHzg1uAgqiT8jZ9nS96Z https://ift.tt/krQSpGa July 21, 2026 at 11:39PM

Show HN: Neuron. Turn a SQL query history into a semantic layer https://ift.tt/EJ6KqhW

Show HN: Neuron. Turn a SQL query history into a semantic layer My cofounder and I previously ran analytics groups in life sciences. That means we led teams of analysts who typed SQL all day long and we ran into common issues of consistency, correctness, and knowledge transfer. We were always one resignation away from losing all of the history on a project or a client. When we left that world we thought we could solve the problem with auto-documentation. Cut to now and we've landed on the modern version of that solution, which is to turn previously executed queries into context for AI. The intuition is roughly this: a smart analyst can read SQL and have a pretty good idea of what's going on, and in fact can infer a lot of institutional knowledge about the domain and how to analyze particular data. LLMs are not great at this (Anthropic and Snowflake have written as much). So we act as the "smart analyst" to pull out institutional knowledge and practices (in the form of SQL) that you can give to an LLM so that it can code like a competent analyst on your team. Right now we're deploying it as a semantic layer population tool. You want to fill up a Genie or Cortex semantic layer? Run our code on your query history, prune it with your experts (delete this, rename that, etc.), and get moving. That can take hours/days instead of weeks. Plus, everything we export is portable to whatever system you choose. FYI we ask for emails on the free trial download so we can monitor our traction and build our network but you don't need to include it if you don't want to. We're hungry for feedback from people who work in the field and are facing these challenges. Major, major thanks in advance for your time. https://ift.tt/tC76ZEl July 20, 2026 at 11:41PM

Show HN: A gallery of browser-based PDF imposition and printing templates https://ift.tt/iRVrcuX

Show HN: A gallery of browser-based PDF imposition and printing templates https://ift.tt/0pizquJ July 19, 2026 at 11:16PM

Show HN: Chalie – AI peer not employee https://ift.tt/E0wY1Jo

Show HN: Chalie – AI peer not employee https://ift.tt/iBwy03z July 20, 2026 at 01:04AM

Show HN: Bribes.fyi – Built something to report bribes https://ift.tt/loeLEDf

Show HN: Bribes.fyi – Built something to report bribes https://bribes.fyi/ July 19, 2026 at 09:01PM

Show HN: Ilya Sutskever's AI reading list into a learning RPG – using kimi k3 https://ift.tt/oS7kIdc

Show HN: Ilya Sutskever's AI reading list into a learning RPG – using kimi k3 I wanted to take kimi k3 for a spin. It turned my simple one sentence prompt to this. Repo here. https://ift.tt/kmT7bNp Well, I'm mindblown. Very humbling for me as a software engineer. Took couple hours for it to build this completely autonomously. And it was all from its mobile app. It couldn't render this though from within the app - it does have a feature to preview any website and publish it on kimi's domain - but it didn't work for this. I had to put it on github pages. It doesn't store anything btw - all progress is tracked in your browser storage. https://ift.tt/29vAF3s July 19, 2026 at 04:24AM

Show HN: RewindCup – explore 23 World Cups on an interactive globe https://ift.tt/DgHjixE

Show HN: RewindCup – explore 23 World Cups on an interactive globe https://rewindcup.com July 19, 2026 at 03:37AM

Show HN: Peek-CLI: Let Claude Code iterate on front end designs https://ift.tt/wD7A6Xy

Show HN: Peek-CLI: Let Claude Code iterate on front end designs https://ift.tt/A6bdolx July 19, 2026 at 12:32AM

Show HN: SDF Pelicans on Bicycle https://ift.tt/187YFOx

Show HN: SDF Pelicans on Bicycle https://ift.tt/liCwALr July 19, 2026 at 12:47AM

Show HN: Tools Berry – client-side calculators with open-source tax engines https://ift.tt/KjuGprP

Show HN: Tools Berry – client-side calculators with open-source tax engines https://ift.tt/J23TfUX July 18, 2026 at 01:08AM

Show HN: Lific: Issue trackers should be simple, right? https://ift.tt/vXMV3gp

Show HN: Lific: Issue trackers should be simple, right? I built Lific because I direct AI coding agents on largish projects and needed somewhere for project state to live that isn't markdown files in the repo. When I was begging to work on long horizon ideas, I started on Linear, but my agent files issues faster than a human does, and I hit their limits and pricing wall almost immediately. Then I self-hosted a popular open source tracker which meant running its 13 containers, and its MCP integration was 30k tokens and I got so fed up that I eventually removed it and went back to .md files for a few weeks. Lific is the opposite shape of most of your self hosted server issue trackers: It's a single Rust binary that uses SQLite, and it has an optimized MCP server built in. Web UI is also included integrated directly into the binary. The simplicity is meant to only apply to the size and the ease of installation. The web UI is fully fleshed out with all of the UX you would expect from an issue tracker like linear. Since I started using lific, my agent flow is that I open the web UI, find a few issues I want to work on, then tell the agent "work on LIF-298, 299 and 301, and if you find bugs, file them as new issues." At the end of the day the project has tracked itself. Issues have statuses, blockers, and comment threads, so "what's workable right now" is a query instead of the agent guessing. Plans are persisted step trees, so a session tomorrow resumes with the same understanding of the goal and the path as the session that made the plan. My largest project has 300+ issues and 100+ docs and agents search it fast. Everything exports to markdown in one click, and the database is just a file on your machine. Setup is ` cargo install ` ` lific init ` ` lific connect ` then pick your harness (OpenCode, Cursor, Claude Code, etc). One honest caveat: on Windows there's no service install yet, so the binary has to be actively running for MCP or Web UI to work on windows. The biggest reason I think Lific is different than a lot of the other options is the lightweight nature of it alongside still having a fully featured web UI. It's meant for self hosters to work on big projects with agents, without sacrificing the other benefits of an issue tracker like a nice management UI or authentication for teams using it. Would genuinely love feedback and bug reports either here or on the discord! https://lific.dev July 17, 2026 at 11:22PM

Show HN: Rudo - A small, elegant dock for Wayland https://ift.tt/BDuXye0

Show HN: Rudo - A small, elegant dock for Wayland https://ift.tt/Jnik7oG July 17, 2026 at 01:12AM

Show HN: Tree, truth, druid, dryad, and tar share one Proto-Indo-European root https://ift.tt/NfSJZhF

Show HN: Tree, truth, druid, dryad, and tar share one Proto-Indo-European root https://ift.tt/cegJMHA July 16, 2026 at 11:11PM