@sandchuck01 · X

Made an oil change reminder web-app with Claude Code: #ClaudeCode #AI #AutoRepair

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,

@kominikedigital · X

Your domain expired. Someone else bought it. Never again. Add your domains once. We email you 30, 7, and 1 day before each one expires.

@DeveloperL92487 · X

I built my first app in 60min And now I got $500 MRR in one month Check here if you are interested It’s a tool to reduce agent token consumption, speed up agent response, and clean up memory cache

@sagaventure · X

i help you get the X profile, posts, comments, etc. as JSON

@Tom721721 · X

Check out what I just built with Lovable!

@urti_luca · X

Sentris finds the exposures in your Supabase app before someone else does.

@LadeLade007 · X

The API-first licensing platform for developers who need subscription, perpetual, or usage-based models without building infrastructure from scratch.

@jay_cobski · X

Awesome oil and gas safety audit tool -

@Outflowchain · X

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

@outagedeck · X

OutageDeck, outage alerts for 168 cloud vendors (AWS, Cloudflare, OpenAI, Slack), built only on their official status feeds. No crowd reports, no scraping, no false positives. Free email alerts for 5 providers + a free JSON API, no key.