Caveat verdict

google-search-2

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Google Custom Search API wrapper using user-supplied GOOGLE_API_KEY and GOOGLE_CX; calls only the official Google Custom Search endpoint with no third-party data routing.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

43
security
30
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="your_google_api_key

Pattern match medium

pip3 install — installs Python packages at runtime

README.md · code · pip3 install

Pattern match low

Python os.getenv — reads environment variable

src/google_search.py · prose · downgraded · os.getenv(

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API