Caveat verdict

adspower-browser

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

The credential access is limited to the ADS_API_KEY for the AdsPower local API, which is the documented authentication mechanism for the stated browser-profile management purpose; no exfiltration to unexpected third parties is present.

⚠ 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
50
transparency
70
maintenance

Permission integrity

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (2)

Pattern match high

Pipe to sh — executes piped content as shell commands

references/country-code.md · prose · downgraded · | sh

Pattern match medium

HTTP request to bare IP address — common in malicious payloads

references/user-proxy-config.md · prose · downgraded · http://127.0.0.1

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A). 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_installcredential_access

Is this flag fair?

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