Is secret-scanner safe to install?

SaferSkills independently audited secret-scanner (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/secret-scanner/SKILL.md · 1 file

skills/secret-scanner/SKILL.md2.3 KB · Markdown

name: secret-scanner

description: "Pre-push API key and credential scanner - blocks git push if secrets found"

version: 1.0.0

category: security

tags: [secrets, api-keys, pre-push, git-hooks, security]

Secret Scanner

Scans your codebase for leaked API keys, tokens, and credentials. Blocks git push if secrets are found.

Usage

# Scan current directory
vibeco secrets

# Scan specific path
vibeco secrets /path/to/project

Detected Secrets (22 patterns)

Provider	Pattern	Example
OpenAI	`sk-proj-...`, `sk-...`	`sk-proj-abc123...`
Anthropic	`sk-ant-...`	`sk-ant-api03-...`
AWS	`AKIA...`	`AKIAIOSFODNN7EXAMPLE`
GitHub	`ghp_...`, `gho_...`, `github_pat_...`	`ghp_xxxxxxxxxxxx`
Stripe	`sk_live_...`, `pk_live_...`	`sk_live_4eC39H...`
Google	`AIza...`	`AIzaSyDaGm...`
Slack	`xoxb-...`, `xoxp-...`	`xoxb-123-456-abc`
SendGrid	`SG....`	`SG.xxx.yyy`
npm	`npm_...`	`npm_xxxxxxxxxxxxx`
PyPI	`pypi-...`	`pypi-AgEIcHl...`
Database URLs	`postgres://`, `mongodb://`, `mysql://`, `redis://`	With embedded passwords
Private Keys	`PRIVATE KEY-----`	PEM format

Auto-Setup: Git Pre-Push Hook

Add to your project's .git/hooks/pre-push:

#!/bin/bash
vibeco secrets "$(git rev-parse --show-toplevel)" || exit 1

Make it executable:

chmod +x .git/hooks/pre-push

Now every git push will scan for secrets first. If any are found, push is blocked.

How It Works

Walks all source files (skips node_modules, dist, .git, lock files)
Matches 22 regex patterns for known API key formats
Skips comments and regex definition lines (avoids false positives)
If secrets found: prints masked values, exits with code 1 (blocks push)
If clean: prints success, exits with code 0

What to Do If Secrets Are Found

Remove the secret from source code
Move to .env file (add .env to .gitignore)
Use environment variables: process.env.API_KEY
If already pushed: rotate the credential immediately (it's compromised)

Scanned File Types

.ts .tsx .js .jsx .mjs .cjs .py .go .java .rb .php .rs .swift .kt .json .yml .yaml .toml .env .cfg .conf .ini .sh .bash .zsh .xml .properties .gradle

secret-scanner— agent skill

Is secret-scanner safe to install?

Secret Scanner

Usage

Detected Secrets (22 patterns)

Auto-Setup: Git Pre-Push Hook

How It Works

What to Do If Secrets Are Found

Scanned File Types

Audit the pieces. Scan the whole. Decide.