SlopScore
00 crowd

vibe-launch-review

A final launch safety gate for vibe-coded apps.
Open repo on GitHubgithub.com/DDDDanteeeeeee/vibe-launch-review
Python · ★ 2 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 1 hour ago by DDDDanteeeeeee · last checked 1 hour ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-19: A final launch safety gate for vibe-coded apps.; its own README says "A final launch safety gate for vibe-coded apps". 2 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as DDDDanteeeeeee. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
A final launch safety gate for vibe-coded apps.
created
2026-06-18 · pushed 2 months ago · 71 commits · 1 contributor
release
v0.1.0 · 2026-06-18
languages
Python 100%
paperwork
contributingpull request templatelicensereadme 85% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 1 hour ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
python
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: A final launch safety gate for vibe-coded apps.; its own README says "A final launch safety gate for vibe-coded apps". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

Vibe Launch Review

A final launch safety gate for vibe-coded apps.

Vibe Launch Review helps builders review AI-generated or vibe-coded products before public launch. It checks the five risk areas from the source video logic: SMS/email abuse, UGC moderation, image/file upload risk, AI prompt/model-call exposure, and demo assumptions that break in public.

It is project-type-aware. The review first asks what kind of product this is, then weights the five gates accordingly. A standalone desktop app with no comments, posts, community, profiles, or shared submissions should not be punished for missing UGC moderation. An AI app with paid model calls should instead receive heavier attention on model-call exposure, budget, quota, monitoring, and demo-to-public readiness.

It is also launch-scope-aware. A controlled paid pilot with prepaid points and manual code issuance should not be judged as if it were a free public self-serve SaaS launch. The report should say what scope is allowed, what scope is blocked, and which gaps matter only before public-scale release.

It now follows a four-stage workflow: Context Intake, five-gate review, Evidence Ledger, and scoped delivery decision. This keeps the review from jumping straight to a verdict before it understands the product, the launch scope, and the freshness of the evidence.

It keeps the user experience simple. Technical users can use it to save review time. Non-technical vibe coders can use it to get a clear launch decision without learning security jargon.

Data and privacy handling is one extra view inside the existing gates, not a new legal-compliance gate. When an app handles files, user content, AI context, model output, or logs, the report adds a short feedback block: what data is involved, where it goes, what log/access/retention/deletion proof exists, and whether this affects the current launch scope.

It does not fix code. It finds launch risks, explains why they matter, and tells the builder what evidence or guardrail class is needed before launch.

It can produce two report styles:

  • An audit record for engineers who need raw five-gate evidence.
  • A product delivery acceptance report for founders, product owners, sales, operations, or other non-technical readers who need a clear launch decision.

Why This Exists

Vibe-coded products can look complete while still being unsafe for real users. The common failure is not that the app cannot run. The failure is that nobody reviews the public abuse surfaces before launch.

This skill is built for that last checkpoint.

What It Reviews

Gate What It Catches
SMS/email interface abuse Paid or spam-capable sends without limits, budget caps, or anomaly monitoring.
UGC moderation Public user content without review, reporting, takedown, or accountability evidence.
Image/file upload Upload paths without size/type/content/access/storage controls.
AI prompt/model-call exposure Prompts, keys, public model routes, quota gaps, and unreviewed model output.
Demo-to-public-product gap Mock auth, debug routes, default accounts, frontend-only permissions, and demo assumptions.

What It Produces

  • A launch verdict: BLOCK_PUBLIC_LAUNCH, PRIVATE_BETA_ONLY, CONDITIONAL_LAUNCH, or PUBLIC_LAUNCH_READY.
  • A project profile and gate applicability table.
  • A five-gate summary table.
  • A compact Evidence Ledger that separates current proof, previous proof, and missing proof.
  • A short data and privacy handling feedback block when user files, AI context, model outputs, or logs matter.
  • Findings with evidence label, evidence, risk, severity, and audit-level recommendations.
  • Evidence gaps that must be resolved before a stronger launch decision.
  • When requested, a plain-language delivery acceptance report covering current status, business flow, verified paths, controlled pilot scope, public-launch blockers, and next work.

What It Does Not Do

  • It does not modify source code.
  • It does not generate patches.
  • It does not configure services.
  • It does not perform penetration testing.
  • It does not replace a full security audit.

Install

Copy this folder into your local Codex skills directory, or install the packaged vibe-launch-review.skill artifact if your environment supports .skill files.

Expected installable layout:

vibe-launch-review/
  SKILL.md
  agents/openai.yaml
  references/

Usage

Ask in the language you want the report in:

Use $vibe-launch-review to review this app before public launch.

For a stakeholder-facing delivery report, ask:

Use $vibe-launch-review to produce a product delivery acceptance report and launch decision for this version.

You can provide:

  • A project directory or repository.
  • A PR, patch, or diff.
  • Product notes, screenshots, routes, storage notes, AI prompt notes, or launch notes.

The report language follows your input language. Code identifiers and status enums stay unchanged.

Demo And Evals

See:

  • examples/function-tests/
  • examples/public-demo-pack.md
  • examples/smoke-review-output.md
  • examples/zh-realistic-vibe-app/
  • evals/evals.json

examples/function-tests/ai-catalog-controlled-pilot-*.md is the calibration case for a desktop app with a cloud model proxy, prepaid points, manual code issuance, and controlled commercial pilot scope.

examples/function-tests/public-self-serve-ai-saas-*.md is the contrast case for a public self-serve AI SaaS where missing rate limits, budget caps, alerts, and circuit breakers should block public launch.

Preflight

Run this before local packaging or publishing:

python scripts/preflight_check.py .
python scripts/validate_functional_outputs.py examples/function-tests/cases.json
python scripts/validate_smoke_outputs.py examples/smoke-review-output.md
python scripts/validate_smoke_outputs.py examples/zh-realistic-vibe-app/review-output.md --expect-language zh

Expected result:

READY_FOR_LOCAL_PACKAGE
FUNCTIONAL_OUTPUTS_OK
SMOKE_OUTPUT_OK
SMOKE_OUTPUT_OK

Build local artifacts:

python scripts/package_release.py . --dist ../dist

License

MIT.

Read the rest on GitHub

Scan report · 2026-09-19
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review — +10 owner has 0 followers

From the balcony · 0 of 4 clapped

    Schnitzel, Cap'm Slop, Princess and Crusoe read it and passed. Their reasons are on the balcony, with every other verdict.

    Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

    0 comments

    log in to comment.

    report this listing — log in to report