Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Github Bounty Hunter
v1.0.1Automatically scan GitHub repositories for bounty issues, filter by difficulty/reward, and auto-submit solutions.
⭐ 0· 573·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill advertises multi-platform bounty hunting, automatic PR creation, payment tracking and 'wallet management', but the included Python code only searches GitHub issues via the 'gh' CLI and posts comments to apply. Registry metadata declares no required binaries or env vars, yet the SKILL.md and code require the GitHub CLI and a GitHub token. The claimed capabilities exceed what the code actually implements.
Instruction Scope
SKILL.md instructs the agent to auto-apply, track payments, and manage wallets; the runtime code only scans GitHub issues, generates a comment-based proposal and comments '/apply'. The instructions also mention other platforms (Gitcoin, Bountysource) which are not referenced in code. There are no instructions to read unrelated host files, but the instructions and code differ in scope.
Install Mechanism
There is no install spec (instruction-only skill with bundled code), which is low risk for arbitrary downloads. SKILL.md claims the 'gh' CLI will be auto-installed if missing, but no install steps are present in the package — so installation behavior is ambiguous and relies on external tooling already present on the host.
Credentials
The skill requires a GitHub account/token and the 'gh' CLI to work, but the registry metadata does not declare any required env vars or binaries. The bundled config.json includes a wallet_address (a donation/receiving address) which suggests payment routing but the code does not perform wallet operations. Missing explicit declaration of required credentials is a notable gap.
Persistence & Privilege
The skill does not request 'always' presence and does not modify other skills or system-wide configs. It writes a local state file in its working directory and runs a continuous loop — expected for a scanning/automation script and within reasonable privilege bounds.
What to consider before installing
This skill has several mismatches between what it promises and what it actually contains. Before installing or running it: 1) Treat the GitHub token requirement as real — only supply a token with minimum scopes and consider using a dedicated test account; the package metadata fails to declare this. 2) Expect that the code uses the 'gh' CLI: ensure 'gh' is installed and authenticated separately (the package does not install it). 3) The README/SKILL.md claim wallet management and multi-platform support, but the code doesn't implement those; the included wallet_address in config.json could be an indicator of where payments are expected to be sent — verify this and do not supply private keys. 4) Running the skill will auto-post comments to issues (auto-applying) — this can trigger rate limits, spam, or ToS violations on your account; consider running on a sandbox/test account first. 5) If you consider installing: review the Python file line-by-line (it uses subprocess.run to invoke 'gh'), remove or modify any automatic apply behavior if you want manual approval, and confirm the author/source before paying. If the author can provide corrected registry metadata (declared env vars/binaries) and clarify the wallet/payment workflow, reassess; until then treat the package cautiously.Like a lobster shell, security has layers — review code before you run it.
latestvk97d9t3eerch90tqt0vn7dd4tn81z1jv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.