Caveat verdict

bounty-automation

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

The skill auto-claims bounty issues, implements solutions, commits, and opens PRs using stored GitHub tokens and OpenTask credentials without per-action human approval; autonomous code-writing and PR-submission using stored developer credentials carries genuine risk of unintended actions.

⚠ 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.

65
security
70
transparency
70
maintenance

Permission integrity

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (1)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="ghp_YOUR_TOKEN

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

package_install

Is this flag fair?

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