live-preview@1.0.6
CAUTION· static onlyPublisher claims: "Share a live preview of a website under development via aitun tunnel, with hot-reload support so users see changes in real time as you edit. Perfect for AI a..." 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-12 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; Pipe-to-shell pattern; Auto-update or dynamic fetch configuration. 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
kill $DEV_PID 2>/dev/nullFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.curl -fsSL https://aitun.cc/install.sh | bashFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.The `aitun` command (installed via `pip install aitun`, or alternatively `curl -fsSL https://aitun.cc/install.sh | bash` / `irm https://aitun.cc/install.ps1 | iex` on Windows) accepts these flags:Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.npx vite --port 8080 --host &Fix: Pin versions and sources; vendor anything fetched at install time.curl -fsSL https://aitun.cc/install.sh | bashFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Start the local dev server with hot-reload enabled. The command depends on your framework:Fix: Pin versions and sources; vendor anything fetched at install time.The `aitun` command (installed via `pip install aitun`, or alternatively `curl -fsSL https://aitun.cc/install.sh | bash` / `irm https://aitun.cc/install.ps1 | iex` on Windows) accepts these flags:Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.kill $AITUN_PID 2>/dev/nullFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 ctz168: 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.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.