Developer Tools1 month ago
DevDiff
Analyzes code diffs and changelogs using AI with your own API keys.
Open source
@eldrex_bula · X
The full gallery
Tech stack
15 projects
Analyzes code diffs and changelogs using AI with your own API keys.
@eldrex_bula · X
Crie um canal privado de feedback com sua marca antes que seus clientes reclamem no Reclame Aqui, redes sociais ou lojas de apps. Widgets, roadmap público e changelog — tudo white
@teles2o · X
Collect product feedback, publish a live roadmap and changelog, maintain a help center, and answer private support requests in one place.
@ahmedqamar0 · X
i have zero users...not even on the free plan..
Privacy‑first, EU‑hosted product feedback, public roadmap, and changelog—built for alignment and customer‑driven delivery. Built for SaaS teams to collect...
@yvesdalyy · X
Create beautiful changelogs and release notes to document and share product updates.
@becomingjed · X
Still building
Convert changelogs into X threads that preserve accurate API and version details.
@BChopLXXXII · X
Hey Jana, 👋 already connected but thought I would drop my product here. I built it helps builders turn their changelogs into X threads without making stuff up. Would love some feedback...
Monitor webpages and OpenAPI specs for changes with Slack, email, and webhook alerts.
epigos · HN
PingChange – monitor web pages and OpenAPI specs for meaningful changes
Notes with code blocks, Kanban bug tracker, and snippet library with GitHub import.
@SinghApurv1711 · X
Hey! Check it out here:
Enterprise memory management dashboard
@dingfengtow_df · X
Just launched: Aristra public beta Agentic platform built on the Aristra Memory System. Persistent context of how you work + always-on agents. Memory is modular, also works with Codex, Claude Code, and other agent systems. Limited spots open.
Debug and monitor AI agents with real-time visualization and performance analytics.
@simranrambles
AI-generated humorous roasts of GitHub developer profiles.
hito20 · HN
I built an AI that roasts GitHub profiles
Compare two npm package versions to identify new or changed files.
fathermarz · HN
I’ve worked in software supply-chain security for six years doing binary analysis on firmware, industrial controls systems, and commodity IT closed/open source software. What I learned is that in hopes to secure the software supply chain we have ran a very similar playbook and mostly over engineered the problem, with SBOMs and VEX documents and expected the industry to comply. But what was discovered was that every SBOM looks different depending on who produced it and at what step in the chain,