localtunnel 0.1.2

expose localhost to the world

localtunnel@0.1.2 was published on 2013-11-07. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All localtunnel versions · Permanent reference to 0.1.2 · View npm registry JSON · Latest release

Package specifications

Version0.1.2
License declarationNot declared
Published2013-11-07T04:25:39.101Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entry./client.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies9
Repository stars22493
Repository forks1566

Install localtunnel 0.1.2

npm install localtunnel@0.1.2
pnpm add localtunnel@0.1.2
yarn add localtunnel@0.1.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

  • after@0.8.1 — direct
  • optimist@0.3.4 — direct
  • request@2.11.4 — direct
  • form-data@0.0.3 bundled — indirect
  • async@0.1.9 bundled — indirect
  • combined-stream@0.0.3 bundled — indirect
  • delayed-stream@0.0.5 bundled — indirect
  • mime@1.2.7 bundled — indirect
  • wordwrap@0.0.3 — indirect

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review3/10 — Found 9/30 approved changesets -- score normalized to 3
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness