AMARCOVECCHIO99

5 ms·

1.
AI Agent Site Score Scanner(prodlint.com)
2 points by AMARCOVECCHIO99 6mo ago|0 comments
2.
Almanack of Agents: Dispatches from an AI Social Network(amazon.com)
1 points by AMARCOVECCHIO99 7mo ago|0 comments
3.
by AMARCOVECCHIO99 7mo ago
gitleaks and trufflehog are great for scanning git history for leaked secrets but that's one of 52 rules. prodlint catches the structural patterns AI coding tools specifically create: hallucinated npm packages that don't exist, se
4.
by AMARCOVECCHIO99 7mo ago
This matches what I've seen. The .env file is one vector, but the more common pattern with AI coding tools is secrets ending up directly in source code that never touch .env at all. The ones that come up most often: - Hardcoded key
5.
by AMARCOVECCHIO99 7mo ago
Haven't used it but just checked it out — interesting project. Different goals though. Raptor configures Claude Code as a security agent for active pentesting and adversarial research. It's an LLM doing dynamic security analysis.
6.
by AMARCOVECCHIO99 7mo ago
I use Cursor and Claude Code daily. The code they write compiles, passes typescript, passes eslint. Then I find a hardcoded Supabase key in a client component, or an import for a package that was never installed, or a server action that tak
7.
Show HN: Prodlint – Static analysis for the bugs AI coding tools write(github.com)
1 points by AMARCOVECCHIO99 7mo ago|3 comments
8.
Show HN: Prodlint – A linter that catches what AI coding tools miss(github.com)
1 points by AMARCOVECCHIO99 7mo ago|0 comments
9.
by AMARCOVECCHIO99 7mo ago
I've been building with AI coding tools for the past year and kept noticing the same patterns in the code they generate: API routes with zero error handling, catch blocks that just do `catch (e) {}`, database queries inside loops, impo
10.
Show HN: Prodlint – Find what AI coding tools miss before production(github.com)
1 points by AMARCOVECCHIO99 7mo ago|1 comments