Is expose-localhost-tunnel safe to install?

SaferSkills independently audited expose-localhost-tunnel (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/expose-localhost-tunnel/SKILL.md · 1 file

skills/expose-localhost-tunnel/SKILL.md1.7 KB · Markdown

name: expose-localhost-tunnel

description: Tunnel/expose a localhost service to the internet from inside a cloud VM — get a stable public HTTPS URL (https://<box>-<port>.on.ascii.dev) with TLS and token-gating built in, no separate daemon or account like ngrok. The VM's dedicated IPv4 also allows raw TCP/UDP and bring-your-own domain. Use to share a preview, expose a webhook target, or open a port.

Expose / tunnel localhost (Box)

Use this when a service running in a Box must be reachable from outside: sharing a dev preview, receiving webhooks, or demoing. Because the service already runs inside the VM, exposing it is one command — no ngrok-style sidecar, no extra account, no cert setup.

Recipe

box ssh "$box_id" -- "cd /app && PORT=3000 npm start &"   # MUST bind 0.0.0.0
box ssh "$box_id" -- "host 3000 --title preview"
box ssh "$box_id" -- "host url 3000"                       # -> https://<box>-3000.on.ascii.dev?_token=...
box ssh "$box_id" -- "host list"                           # manage; host hide <port> to revoke

Ascii terminates TLS for on.ascii.dev and proxies to the box. URLs are token-gated by default (--public drops the token, --private enforces it).

Why Box beats a tunnel tool

No separate daemon/account — the route lives with the VM.
TLS + auth handled; URL stable across the box's life.
Dedicated IPv4 + full TCP/UDP — non-HTTP servers and BYO domains work; most sandbox providers can't tunnel raw TCP/UDP at all.

Prereqs

curl -fsSL https://box.ascii.dev/install | sh, then box login "$BOX_API_KEY" --json.

Gotchas

App must bind `0.0.0.0`. For a URL that outlives a long session, pair with box extend <id> --no-auto-stop. EU-only region today.

expose-localhost-tunnel— agent skill

Is expose-localhost-tunnel safe to install?

Expose / tunnel localhost (Box)

Recipe

Why Box beats a tunnel tool

Prereqs

Gotchas

Audit the pieces. Scan the whole. Decide.