repo-runner@1.0.2
CAUTION· static onlyPublisher claims: "Bootstrap and run a GitHub project by following its docs (README/docs), with safeguards for untrusted install/run steps. Use when the user gives a GitHub rep..." 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-20 and scored it 58/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: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. 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
- Never paste or store secrets. If `.env` is needed, ask user to provide values out-of-band.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [[ -f .env.example && ! -f .env ]]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "env_hint=.env.example exists; consider copying to .env (ask user for values)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Before running `npm/pnpm/yarn install` (or any `curl | bash`), ask for confirmation.Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- If `.env.example` exists, copy to `.env` **only after confirmation**Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Before running `npm/pnpm/yarn install` (or any `curl | bash`), ask for confirmation.Fix: 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
22 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zyl-hub: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.