Skills/ClawHub/vibecheck

vibecheck@1.0.11

CAUTION· static only

Publisher claims: "Audit AI-generated code before shipping. Static + AST scan for hardcoded secrets, SQL injection, eval/exec, shell injection, unsafe deserialization and TLS issues, with severity-capped 0-100 scoring and SARIF/JSON/Markdown reports. Optional autofix - every current fix changes behavior and requires the explicit --fix-unsafe opt-in; baseline export for legacy code. Zero-dependency Python CLI." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher thiennhant95 · publishing for 1 daysInstalls 63Last detonated 26 min ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-15 and scored it 60/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Access to sensitive file pathsvibecheck.py:110 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"title": "Hardcoded secret in a .env file",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsvibecheck.py:43 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".json", ".toml", ".env", ".cfg", ".ini", ".tf",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:79 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- Unquoted `KEY=value` secrets are checked only in `.env*` files; split secrets can evade.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsvibecheck.py:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesloaders, os.system), .env secret detection, severity-capped scoring,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsvibecheck.py:51 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesr"(?i)(example|placeholder|your[-_]|changeme|xxx+|<[^>]+>|\$\{|getenv|environ|process\.env|config)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsvibecheck.py:111 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"advice": "Move real values out of .env into a secret manager; commit only .env.example.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈1,060 tok
1 file · 8 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

20 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim thiennhant95: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim thiennhant95Propose a patch to the maintainer