vws-helper@1.0.2
CAUTIONPublisher claims: "Use this skill whenever the user or agent needs to manage one or more virtual workspaces with vwsd/vws. vwsd prepares real, git-backed workspace directories: remote git sources become real `git worktree` directories created directly under the workspace mountpoint, and local directory sources are used in place (auto `git init` if needed). There is no NFS/FUSE mount, no symlink, no copy-on-write overlay. Trigger on keywords: vwsd, vws, virtual workspace, workspace mount, workspace unmount, workspace config, multi-workspace, parallel workspaces, workspace management, mounting git repos, workspace init, workspace doctor, workspace list, git worktree workspace." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 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: 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
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 albert-lv: 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.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.