RedHub AIRedHub AI
Tool Gate · How it works

How the gate works

How the Vibe-Coded App Pre-Launch Security gate works

This tool grades one vibe-coded app before it ships. It scores 6 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.

The 6 weighted controls

01Secrets out of the client bundle & repowt 22
02Server-side auth on every sensitive routegate · scored 0 - forces DO NOT SHIP regardless of the 78 scorewt 22
03Input validation & injection defensewt 16
04Dependency & supply-chain integritywt 14
05No verbose errors, debug, or source maps in prodwt 12
06Access control actually testedwt 14
LAUNCH-READY
score 75+
HARDEN FIRST
score 50+
DO NOT SHIP
below floor
Fatal-control · worsen-only

Secrets out of the client bundle & repo and Server-side auth on every sensitive route are both fatal controls - either one scored 0 (Absent) forces DO NOT SHIP no matter the score.

78/100
DO NOT SHIP

Why: Every other control reads Solid - secrets are clean, inputs validated, dependencies audited, errors hidden, access tested - for a weighted score of 78, which would normally read LAUNCH-READY. But server-side auth is completely Absent (0/2), a fatal control. The gate forces DO NOT SHIP regardless of the 78.

Fix firstServer-side auth on every sensitive route - the fatal control sitting at Absent; lift it to at least Partial and the gate releases.

A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Runs entirely in your browser and resets on reload. Scores the app you describe, not people. Not a substitute for a professional penetration test.