Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
gerritaction
v0.1.0Query Gerrit accounts, changes, groups, or projects and perform actions like adding reviewers, approving, submitting, or deleting changes via the Gerrit API.
⭐ 0· 99·0 current·0 all-time
byJia@craftslab
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description (Gerrit queries and change actions) align with the SKILL.md: it describes queries and actions against a Gerrit API and requires a config file with Gerrit host, user, and password.
Instruction Scope
SKILL.md is specific about commands, required config fields, and when to use query-only runs vs destructive actions; it does not instruct reading unrelated files or exfiltrating data to external endpoints.
Install Mechanism
No install spec in the registry (instruction-only), but the SKILL.md repeatedly requires running `pip install gerritaction`. Installing an unvetted PyPI package is moderate risk because package provenance and contents are unknown — the skill does not provide a trusted source or checksum.
Credentials
The skill needs Gerrit credentials (user/pass in the provided config.yml) but the registry metadata declares no required credentials or primaryEnv. This mismatch (credentials required by runtime but not declared) is an incoherence that could hide risks (cleartext credentials in config.yml, unclear credential storage expectations).
Persistence & Privilege
always is false, skill is instruction-only and does not request elevated or persistent system privileges or modify other skills' configs.
Scan Findings in Context
[no_code_files_to_scan] expected: The provided package is instruction-only (SKILL.md + config.yml). The regex scanner had no code files to analyze, so there are no pattern matches to report.
What to consider before installing
Before installing or using this skill: 1) Verify the origin and integrity of the Python package `gerritaction` (PyPI page, source repository, maintainer identity and recent activity). 2) Prefer not to store plaintext credentials in a repo-tracked config.yml; use a secure vault or environment variables and confirm how the CLI accepts secrets. 3) Run any actions in query-only mode first and test in a non-production Gerrit instance. 4) Consider installing and running the CLI in an isolated environment (virtualenv or container) so you can inspect the installed package files. 5) The registry metadata should declare required credentials — treat the omission as a red flag and ask the publisher for clarification or a trustworthy source before proceeding.config.yml:7
Install source points to URL shortener or raw IP.
About static analysis
These patterns were detected by automated regex scanning. They may be normal for skills that integrate with external APIs. Check the VirusTotal and OpenClaw results above for context-aware analysis.Like a lobster shell, security has layers — review code before you run it.
latestvk975cxq66xbeqgrpmwytgebh1n835c6x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.