worktree-manager@1.0.3
CAUTION· static onlyPublisher claims: "Manage Docker-based dev instances and git worktrees. Handles app container lifecycle, database seeding, and proxy route activation. Requires mysql-manager an..." 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-22 and scored it 63/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
Each instance gets its own docker-compose stack (backend + frontend), isolated git branch, and `.env.worktree-<name>` file. MySQL and nginx-proxy are managed separately by their own plugins.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "$BASE_DIR/.env.worktree-$name"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `worktree` → `.env.worktree-<name>`, checked out at `.worktrees/<name>`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- If `./run.sh` is not executable: `chmod +x run.sh`Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.if [ "$env_f" = "$BASE_DIR/.env.base" ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "$BASE_DIR/.env.base"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.├── .env.worktree-<name> # per-worktree env (gitignored)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.for env_f in "$BASE_DIR/.env.base" "$BASE_DIR"/.env.worktree-*; doFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `main` → `.env.base`, project rootFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.├── .env.base # main instance envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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
17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim pereirajair: 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.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.