
attestd | CVE API for Machine-Readable Vulnerability Risk Signals
Convert CVE data into machine-readable risk signals for AI agents and automation.
robert_marshall5 · Product Hunt
attestd CVE and supply chain risk signals for autonomous AI agents.
The full gallery
Tech stack
60 projects

Convert CVE data into machine-readable risk signals for AI agents and automation.
robert_marshall5 · Product Hunt
attestd CVE and supply chain risk signals for autonomous AI agents.

@suni_code https://t.co/OajI3lOKKW - Traffic Orchestration Platform
@KsaAZaks · X
- Traffic Orchestration Platform

AI-powered notes app built with Codex and refined with Grok.
@Number1AIFanboy · X
I got to go to bed. More coding tomorrow. I just had a realization that I'm building cool shit, using @grok in an app that I built with Codex and refined with Grok. And now Grok just works on himself. LFG🚀 Drop me a note here: Get the app here (use LAUNCH50):

AI-powered platform for intuitive vibe-based coding development.
@isuryatk · X
- World's most reliable vibe coding platform

Two AI reviewers analyze your code independently and verify each other's bug findings.
@BotariaDotBot · X
This Tuesday I'm launching Botbugger on @ProductHunt 🚀 One AI reviewer gives you 10 "critical" bugs — half hallucinated. So I built two: Claude Code + Codex review your code independently, then cross-check each other. Real bugs with fixes, not noise.

Manage API keys and usage budgets for coding-agent workflows with request routing.
u/Zyron_X · Reddit
I built a service for people to use Codex API without 5-hour limit disruption I built a small service for people who use the OpenAI Codex API regularly and want more predictable usage without the 5-hour or weekly limits. It currently provides: Frontier OpenAI models (GPT 5.6 family included) Managed API key Monthly usage budgets depending to plan No 5-hour limit No weekly limit Under the hood, it is built on top of an open-source project and proxies requests to

Analyze pull requests to understand changes, distinguish important modifications from trivial ones, and identify potential regressions.
logphase · HN
I've always struggled to hold a large PR in my head. AI-assisted coding has made it worse. Especially when dozens of files are modified, it became harder to understand what changed: distinguishing important changes from trivial ones and identifying if regressions were introduced. I was also tired of switching between file and method to build the whole picture in my head — I wanted all the context at the point of the function I was reviewing. I guess I'm just more of a visual person. I realized t

LeetCode-style Python practice for agentic AI interviews covering ReAct loops, RAG, and tool calling.
@notunknownkyun · X
- leetcode style interview prep for agentic AI interviews and unskilling folks.

Write objectives and let AI agents (Claude, Cursor, Codex) decompose and execute coding tasks.
dudemanAtl · HN
PlanWright – A control plane for AI coding agents

Gate any REST API with per-request USDC payments, settling instantly on-chain.
@0xanukul · X

Browse 5675+ Midjourney --sref codes and style references to customize your AI-generated images.
Midjourney 样式代码库 — SrefHunter 汇集各种社交媒体平台的 Midjourney 样式代码

Scan GitHub repos for security vulnerabilities and code issues, then auto-fix them.
u/Still_Amphibian545 · Reddit
almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex