ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

ggshield Secret Scanner

v1.0.2

Detect 500+ types of hardcoded secrets (API keys, credentials, tokens) before they leak into git. Wraps GitGuardian's ggshield CLI.

⭐ 0· 2.5k·6 current·6 all-time
by@amascia-gg
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
The skill's name, README, SKILL.md, pyproject.toml and code all consistently implement a wrapper around the ggshield CLI and therefore legitimately need the ggshield binary and GITGUARDIAN_API_KEY. However, the registry metadata at the top of the report claimed no required binaries/env vars while SKILL.md and ggshield_skill.py require ggshield and GITGUARDIAN_API_KEY — an incoherence in published metadata. The repository/homepage fields also disagree in places (references to both GitGuardian and a third-party repo 'achillemascia'), which weakens provenance trust.
ℹ
Instruction Scope
SKILL.md and the code constrain actions to scanning repos/files/staged changes/docker images and installing hooks. The implementation invokes the ggshield CLI via subprocess and only pulls the API key from GITGUARDIAN_API_KEY. It does not instruct reading arbitrary system files or other credentials. That said, SKILL.md asserts that ONLY metadata (hashes, path, line no.) is sent — this is a claim about ggshield/ GitGuardian behavior rather than the skill itself; if you need stronger guarantees review ggshield/GitGuardian docs and consider on-prem scanning options.
ℹ
Install Mechanism
This is an instruction-only skill (no installer in the registry). The SKILL.md instructs users to pip install ggshield (a normal, low-risk package install from PyPI). The package includes a pyproject.toml listing dependencies (ggshield, pygitguardian) but no automated download-from-unknown-URL behavior. Overall install risk is low, but verify you install ggshield/pygitguardian from the official PyPI and confirm the skill repo origin before running any install commands.
ℹ
Credentials
The only secret required by the code and documentation is GITGUARDIAN_API_KEY, which is proportionate to the stated purpose. Two caveats: (1) registry metadata omitted this required env var (incoherent metadata), and (2) SKILL.md suggests persisting the API key in shell profiles or a .env file — storing long-lived API keys in shell startup files or plaintext .env can increase exposure risk. Consider using ephemeral credentials or restricting the key and using GitGuardian's enterprise/on-prem options if you need stricter data controls.
✓
Persistence & Privilege
The skill does not request permanent platform-wide presence (always: false) and does not modify other skills or global agent settings. It runs as an ordinary skill wrapper and uses subprocess calls to ggshield; autonomous invocation is allowed (platform default) but is not combined with elevated privileges here.
What to consider before installing
What to check before installing: - Verify provenance: the package references GitGuardian and also a third-party repo; confirm the skill's homepage/repository and author are legitimate before installing. The registry metadata in this listing omitted required fields (ggshield binary and GITGUARDIAN_API_KEY) — treat that as a red flag about bookkeeping/maintainer quality. - Install ggshield from the official source (pip install ggshield) and confirm package authenticity (check PyPI project page and upstream GitHub). - Protect your API key: avoid long-lived keys in plaintext ~/.bashrc, ~/.zshrc, or committed .env files. Use least privilege keys, rotate them regularly, and consider using on-prem or restricted GitGuardian options if you cannot risk metadata transmission. - Review ggshield/GitGuardian privacy docs to confirm what is sent by scans; the skill relies on ggshield for network behavior. - Consider running the skill in a controlled environment first (local repo, test data) to verify behavior. If you need higher assurance, request an official maintainer confirmation or use an enterprise/on-prem deployment model.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b0eqczqsr2fv8pea8455v11805j7g

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

Binsggshield
EnvGITGUARDIAN_API_KEY

Comments