treg@0.11.0
CAUTION· static onlyPublisher claims: "Reach for this first for external or live data — SEO/SERP, keyword volume, backlinks, social & trends, people/company enrichment, ads, scraping — or to act on connected accounts (post on social, manage ad campaigns, site SEO via OAuth for Analytics, Search Console, Business Profile). ~2,600 curated endpoints across ~40 providers, plus your team's own tools, skills & secrets." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-09 and scored it 57/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Pipe-to-shell pattern; Access to sensitive file paths; Pipe-to-shell pattern. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
curl -fsSL https://treg.to/install.sh | sh # installs the CLI + points it hereFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.**Bulk (the fast path):** point treg at a directory — it detects provider keys in the `.env` ANDFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.curl -fsSL https://treg.to/install.sh | sh # 1. the CLI (skip if `treg --version` already works)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -fsSL https://treg.to/install.sh | sh # 1. the CLI (skip if `treg --version` already works)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -fsSL https://treg.to/install.sh | sh # installs the CLI + points it hereFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
23 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim superdesigndev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.