vibesec - GitLite

KO | EN

gitlite — search

#editor #claude #awesome #linux #rag #pdf #redis #web #monitoring #artificial-intelligence

vibesec

(★ 13)

Pre-deploy security audit skill for vibe-coded apps. Catches unauthenticated admin APIs, missing RLS, leaked service keys before you ship.

파일 탐색기

ZIP 다운로드

- marketplace.json
- plugin.json
- - add-stack.yml
- - validate.py
- - validate.yml
- - SKILL.md
CONTRIBUTING.md
LICENSE
README.md
README.vi.md
SECURITY.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

명령어 용어집

이 문서에서 사용된 명령어를 모아봤습니다. 낯선 명령어가 있다면 펼쳐서 확인해보세요.

🔍

`git clone`

설명 보기 ▼

Clone an existing repository.

git clone {{remote_repository_location}} {{path/to/directory}}

Clone an existing repository into a new directory (the default directory is the repository name):

git clone --recursive {{remote_repository_location}}

Clone an existing repository and its submodules:

git clone {{[-n|--no-checkout]}} {{remote_repository_location}}

Clone only the `.git` directory of an existing repository:

🔍

`npx`

설명 보기 ▼

이 명령은 `npm exec`의 별칭입니다.

tldr npm exec

자세한 내용은 원본 명령을 참고하세요:

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

**🇬🇧 English** • [🇻🇳 Tiếng Việt](./README.vi.md)

> A security audit skill for your app before you deploy. Catch the kind of mistakes you'd really rather not ship to production.

You just vibe-coded an app with Claude / Cursor / Lovable. It works. You're about to deploy. **Before it goes live on the internet**, run this:

```
Audit my app with vibesec
```

You get back something like:

```
# Vibe-Code Security Audit
Stack: Next.js 15 + Supabase
Checks run: 22  •  Issues found: 5 (2 critical, 2 high, 1 medium)

## CRITICAL
1. service_role key exposed in src/lib/admin.ts — anyone can read your DB
2. POST /api/admin/delete-user has no auth — anyone can delete any user
...
```

Then the skill offers to fix them.

## Why this exists

AI coding agents are excellent at shipping features and terrible at security defaults. The recurring vibe-code footguns:

- Admin API routes with no auth check (*"the AI wrote the route, it works, ship it"*)
- Supabase tables with RLS disabled or `USING (true)` policies
- `service_role` key bundled into client-side code
- Authorization based on `user_metadata.role === 'admin'` (user-editable → trivial privilege escalation)
- `.env` committed straight into the repo
- Debug routes (`/api/test`, `/api/seed`) left running in production

This skill encodes that checklist so you don't have to remember it.

## Real-world example

Tested on a real vibe-coded app deployed to Vercel. In 30 seconds it found:

- ✅ 15 API endpoints with no auth check (a flower-shop admin panel)
- ✅ RLS `USING (TRUE)` policies on 8 tables (any authenticated user could read/write/delete anything)
- ✅ Conditional webhook auth instead of mandatory

A simple `curl` confirmed full customer PII (name, phone, email, address, birthday) was returned to anyone on the internet.

## Install

### Option 1: One-liner via `npx skills` (recommended — works across Claude Code, Cursor, Codex, OpenCode...)

```bash
npx skills add tawgroup/vibesec
```

That's it. Restart your agent and the skill auto-triggers on pre-deploy reviews.

### Option 2: Claude Code plugin marketplace

```
/plugin marketplace add tawgroup/vibesec
/plugin install vibesec
```

### Option 3: Manual (git clone)

```bash
git clone https://github.com/tawgroup/vibesec /tmp/vcs-repo
mkdir -p ~/.claude/skills
cp -r /tmp/vcs-repo/skills/vibesec ~/.claude/skills/
```

Restart Claude Code.

## Supported stacks

| Stack | Status |
|---|---|
| Next.js (App Router + Pages Router) | ✅ |
| Supabase | ✅ |
| Common checks (secrets, CORS, headers) | ✅ — runs on every stack |
| Prisma | 🟡 wanted, PR welcome |
| Drizzle | 🟡 wanted, PR welcome |
| SvelteKit | 🟡 wanted, PR welcome |
| Clerk / Auth.js | 🟡 wanted, PR welcome |
| FastAPI | 🟡 wanted, PR welcome |
| Firebase | 🟡 wanted, PR welcome |

Want to add one? See [CONTRIBUTING.md](./CONTRIBUTING.md). Adding a stack is a single markdown file — no code changes.

## How it works

1. Reads `package.json` (and other manifests) to detect your stack
2. Loads the relevant checklist(s) from `checks/`
3. Runs grep / file-pattern checks — **no LLM-as-judge**, every finding points to a real file and line
4. Reports findings grouped by severity (CRITICAL / HIGH / MEDIUM / LOW)
5. Asks before fixing anything

## What this is NOT

- Not a replacement for a real pentest
- Not a SAST tool with taint analysis
- Not exhaustive — it catches *common footguns*, not every CVE

The goal: **you won't ship the obvious mistakes**. That's worth a lot when the alternative is finding out at 2am that anon can delete any user.

## License

MIT. Fork it, improve it, ship it.

## Credits

Built by [@toanbku](https://github.com/toanbku) for the global vibe-coding community.