PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

How to maintain code quality standards with AI code and vibe coding

aikido.dev | blog | #ai-security | #appsec | #devsecops | #code-review | #developer-security | #secure-coding | #technical-debt | #vibe-coding | #code-quality | #ai-coding
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

As AI-written code piles up faster than review can absorb, technical debt compounds until shipping slows; the piece covers pull-request quality checks and why model self-review is not enough.
Published
Collected

Related coverage

blog · borghq.io
Security Review for AI-Generated Code: What Changes Before Merge
More of every pull request is machine-drafted and the bug classes have not changed. What security review must catch in the diff before merge, and what it cannot.
blog · netspi.com
Performing Code Reviews to PCI Requirements
A NetSPI post maps PCI requirements to the OWASP Top 10 for code reviews, noting gaps like track-data retention rules that OWASP does not cover, since no single PCI code-review checklist exists.
blog · aikido.dev
Vibe Check: The vibe coder’s security checklist
Vibe coding with AI tools like Cursor, Lovable, and v0 makes shipping fast, but generated code can leak API keys and invite SQL injection. This checklist covers essential safeguards before you deploy.
blog · about.gitlab.com
Unblock agentic software delivery with governed code review
Client-side review helps the author move faster. Repo-side review on Duo Agent Platform certifies every merge request against rules you set once, at a flat $0.25 rate per review.
blog · jfrog.com
Agentic Development Security is a Discipline that Starts Before the First Line of Code
Agentic development security starts before code: govern what coding agents produce and what they consume—MCP servers, skills, plugins, access—because you can only block artifacts you inventory.
blog · bugbunny.ai
Secure Software Development Lifecycle: Building Security Into the Work
Building security into normal delivery: the SSDLC guide argues security decisions must land at design review, feature kickoff, PR and release time—not as a late gate once architecture is locked.
Back