SlopScore
00 crowd

VibeGuard-AI-Pluging

AI-powered security scanner for vibe-coded applications β€” detect vulnerabilities, secrets, XSS, insecure configurations, and more before you ship. πŸ›‘οΈ My Website link access more open source project
Open repo on GitHub Open the demogithub.com/speakcoreofficial-stack/VibeGuard-AI-Pluging
TypeScript Β· β˜… 3 Β· 0 forks Β· MIT Β· paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)pluginsecurity
listed 1 hour ago by speakcoreofficial-stack Β· 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-17: AI-powered security scanner for vibe-coded applications β€” detect vulnerabilities, secrets, XSS, insecure confi; its own README says "AI-powered security scanner for vibe-coded applications β€” detect vulnerabilities, secrets, XSS, insecure configurations, and more before you". 3 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 speakcoreofficial-stack. 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
AI-powered security scanner for vibe-coded applications β€” detect vulnerabilities, secrets, XSS, insecure configurations, and more before you ship. πŸ›‘οΈ My Website link access more open source project
website
https://ankit-kr.vercel.app/
topics
pluginsecuritysecurity-toolsvibe-coding
created
2026-09-07 Β· pushed 1 week ago Β· 3 commits Β· 1 contributor
languages
TypeScript 95%Shell 5%
paperwork
licensereadme 42% 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
pluginsecurity
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
shelltypescript
topic (detected)
pluginsecuritysecurity-toolsvibe-coding
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: AI-powered security scanner for vibe-coded applications β€” detect vulnerabilities, secrets, XSS, insecure confi; its own README says "AI-powered security scanner for vibe-coded applications β€” detect vulnerabilities, secrets, XSS, insecure configurations, and more before you". 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

πŸ›‘οΈ VibeGuard AI

AI-Powered Security Scanner for Vibe-Coded Applications

Your AI coding agent writes the code. VibeGuard checks the security.

VibeGuard AI is an open-source security scanner designed for modern applications built with AI coding tools, no-code/low-code platforms, and vibe-coding workflows.

It scans your project source code for potential security issues and provides clear findings, confidence levels, and recommendations.


✨ Features

  • πŸ” Security vulnerability scanning
  • 🚨 Severity-based findings
  • 🎯 Confidence score for findings
  • πŸ›‘οΈ Potential XSS detection
  • πŸ” Authentication & authorization checks
  • πŸ”‘ Secret and credential detection
  • 🌐 API security checks
  • πŸ“¦ Dependency security analysis
  • βš™οΈ Security configuration checks
  • πŸ€– AI-assisted security analysis
  • πŸ“„ Multiple report formats (JSON, Markdown, HTML, SARIF)
  • πŸ”„ Git diff scanning (--diff)
  • πŸ’» CLI-based workflow
  • πŸ”Œ VS Code / Cursor integration
  • πŸ§‘β€πŸ’» Designed for vibe-coded applications

πŸš€ Installation

Requirements

Before installing VibeGuard, make sure you have:

  • Git
  • Node.js
  • npm

Check your installation:

git --version
node --version
npm --version

πŸ“₯ 1. Clone the Repository

Clone VibeGuard from GitHub:

git clone https://github.com/speakcoreofficial-stack/VibeGuard-AI-Pluging.git

Enter the project:

cd VibeGuard-AI-Pluging

Check the project files:

dir

On macOS/Linux:

ls

πŸ“¦ 2. Install Dependencies

Inside the VibeGuard-AI-Pluging directory, run:

npm install

Wait until the installation completes successfully.


πŸ”¨ 3. Build VibeGuard

Build the CLI:

npm run build

After the build completes, verify that the CLI exists.

Windows PowerShell:

Test-Path .\packages\cli\dist\index.js

The expected result is:

True

If the result is True, the VibeGuard CLI has been successfully built.


▢️ 4. Test the CLI

You can test VibeGuard directly without installing the global command.

From the VibeGuard repository:

node ./packages/cli/dist/index.js version

If a version number is displayed, the CLI is working correctly.

Example:

VibeGuard 0.1.0

πŸ”Ž 5. Scan Your Project

VibeGuard is designed to scan your own project or a project you are authorized to test.

For example, suppose your project is located at:

D:\aditya\my-project

Move into your project:

cd D:\aditya\my-project

Then run VibeGuard:

node D:\aditya\VibeGuard-AI-Pluging\packages\cli\dist\index.js scan

VibeGuard will analyze the project and report potential security findings.


πŸ“Š Example Finding

VibeGuard may report findings like:

[HIGH] Potential XSS: Unsafe HTML rendering

File: src/components/Example.tsx
Confidence: 70%

Recommendation:
Use safe rendering methods or sanitize untrusted HTML
before rendering.

Each finding can include:

  • Severity
  • Vulnerability type
  • File location
  • Confidence score
  • Recommendation
  • Evidence

πŸ§ͺ Scan Options

Scan the entire project

vibeguard scan

Scan a specific file

vibeguard scan --file src/auth.ts

Scan only changed files (git diff)

vibeguard scan --diff

AI-assisted scan

vibeguard scan --ai

CI mode

vibeguard scan --ci

Report format output

vibeguard scan --format json
vibeguard scan --format markdown
vibeguard scan --format html
vibeguard scan --format sarif
vibeguard scan --format json -o report.json

Initialize project config

vibeguard init

Note: The vibeguard command requires the CLI to be installed globally. If it is not available on your system, use the direct Node.js command shown in the installation section.


πŸ› οΈ Global CLI Installation

If you want to use:

vibeguard scan

instead of:

node ./packages/cli/dist/index.js scan

install VibeGuard globally from the cloned repository (run from the packages/cli directory):

cd packages/cli
npm install -g .

Then verify:

vibeguard version

Expected output:

VibeGuard 0.1.0

If the command is recognized, you can scan your project with:

cd path/to/your-project
vibeguard scan

Replace path/to/your-project with the actual path of your project.


πŸ’» VS Code & Cursor

VibeGuard is designed to work with VS Code and Cursor.

Build the extension:

cd packages/vscode
npm install

Install the VS Code extension packaging tool:

npm install -g @vscode/vsce

Create the VSIX package:

vsce package

This will generate a .vsix file.

Install the VSIX

In VS Code or Cursor:

Extensions
    ↓
...
    ↓
Install from VSIX
    ↓
Select the generated .vsix file

After installation, VibeGuard can be used directly from the editor.


πŸ”Œ Agent Plugins (opencode + Claude Code)

VibeGuard includes plugins so your AI coding agent scans automatically.

opencode

npm run build -w @vibeguard/integrations
cp packages/integrations/dist/opencode/opencode.js .opencode/plugin/opencode.js

Or reference it from opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["/absolute/path/VibeGuard-AI-Pluging/packages/integrations/dist/opencode/opencode.js"]
}

What you get:

  • A vibeguard_scan tool the agent can call
  • A /vibeguard-scan command for a readable summary + fix discussion
  • An auto security hint after every edit/write that introduces findings

Restart opencode after adding the plugin.

Claude Code

mkdir -p .claude-plugin
cp -r packages/integrations/claude/. .claude-plugin/

What you get:

  • /vibeguard command β€” runs npx vibeguard scan and explains findings
  • vibeguard-scan skill β€” automatically triggers when generating code or when asked "is this code secure?"
  • post_tool_use.sh hook β€” post-edit security hint for source files

πŸ§ͺ Example Vulnerable Application

VibeGuard includes example applications for testing the scanner.

Navigate to the example:

cd examples/vulnerable-app

Then run:

node ../../packages/cli/dist/index.js scan

This allows developers to test VibeGuard locally without scanning an external application.

Expected result (intentionally vulnerable example):

Critical: 1   High: 4
Security Score: 40/100
[CRITICAL] Possible exposed API credential
[HIGH] Vulnerable dependency detected: express
[HIGH] Vulnerable dependency detected: axios
[HIGH] Potential XSS: Unsafe HTML rendering
[HIGH] Potential Missing Authorization

πŸ—οΈ Project Structure

VibeGuard-AI-Pluging/
β”‚
β”œβ”€β”€ packages/
β”‚   β”œβ”€β”€ core/                 # @vibeguard/core β€” scanners, findings, reporter
β”‚   β”œβ”€β”€ cli/                  # vibeguard β€” the CLI
β”‚   β”œβ”€β”€ vscode/               # VS Code / Cursor extension
β”‚   β”œβ”€β”€ ai/                   # @vibeguard/ai β€” AI reviewer
β”‚   └── integrations/         # opencode + Claude Code plugins
β”‚
β”œβ”€β”€ examples/
β”‚   └── vulnerable-app/
β”‚
β”œβ”€β”€ README.md
β”œβ”€β”€ LICENSE
└── package.json

πŸ” Security Philosophy

VibeGuard is designed as a defensive security tool.

It focuses on helping developers identify and fix security problems in applications they own or are authorized to test.

VibeGuard should not be used to access, attack, or test systems without permission.

VibeGuard is local-first: your source code is scanned on your machine by default and never uploaded unless you explicitly enable an AI provider.


🎯 Why VibeGuard?

Modern AI coding tools can generate applications extremely quickly.

However, AI-generated code can also introduce:

  • insecure authentication
  • missing authorization
  • exposed secrets
  • unsafe input handling
  • insecure APIs
  • vulnerable dependencies
  • unsafe configuration
  • XSS risks

VibeGuard acts as a security layer between AI-generated code and production.

AI Coding Agent
       ↓
   Generated Code
       ↓
   πŸ›‘οΈ VibeGuard
       ↓
Security Analysis
       ↓
Findings + Recommendations
       ↓
   Safer Application

πŸ—ΊοΈ Roadmap

V1

  • CLI foundation
  • Source-code scanning
  • Security findings
  • Severity levels
  • Confidence scores
  • Basic XSS detection
  • Secret detection
  • Dependency scanning
  • Single-file scanning (--file)
  • Git diff scanning (--diff)
  • AI explanations (--ai)
  • CI mode (--ci)
  • JSON / Markdown / HTML / SARIF reports
  • VS Code + Cursor extension
  • opencode + Claude Code plugins
  • Improved false-positive filtering
  • Finding deduplication
  • Authentication analysis

V2

  • GitHub Actions
  • Pull Request security comments
  • Python support
  • Go support
  • Java support
  • PHP support
  • Advanced data-flow analysis

V3

  • AI security agent
  • Architecture analysis
  • Runtime verification
  • Automated security verification
  • Continuous security monitoring

🀝 Contributing

Contributions are welcome!

1. Fork the repository

git clone https://github.com/speakcoreofficial-stack/VibeGuard-AI-Pluging.git

2. Create a branch

git checkout -b feature/my-feature

3. Make your changes

4. Test your changes

Read the rest on GitHub

Scan report Β· 2026-09-17
  • βœ“ Prohibited terms or links
  • βœ“ Repository eligibility
  • βœ“ slopscore.md paperwork
  • βœ“ Content policy
  • βœ“ Risk review

From the balcony Β· 0 of 4 clapped

    Princess, Crusoe, Schnitzel and Cap'm Slop 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