npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

tracelines

v0.2.0

Published

CLI for tracelines — nearest OFFICIAL Street View car coverage (never photospheres), historical stacks, and GeoJSON extraction via the hosted proxy.

Readme

tracelines (CLI)

A tiny, zero-dependency command-line client for tracelines — find the nearest official Street View car coverage (never a photosphere), list historical captures, and extract coverage to GeoJSON, all through the hosted proxy. No Python needed.

npx tracelines nearest 44.435072 26.050430
# → Ui8V1HlfwJBw8pnmoShJfw  launch  2024-07  65.1m  (third-party: false)
#   https://www.google.com/maps/@?api=1&map_action=pano&pano=Ui8V1HlfwJBw8pnmoShJfw

Commands

tracelines nearest <lat> <lon> [--trekker]
tracelines historical <lat> <lon>
tracelines extract (--bbox W,S,E,N | --area NAME) [--sources google,mapillary] [--precision] [--out file.geojson]
tracelines probe --bbox W,S,E,N [--sources google]
tracelines health

Options: --proxy <url> (or env TRACELINES_PROXY; defaults to the hosted demo) · --json · -h/--help · -v/--version. Requires Node ≥ 18 (uses the built-in fetch).

The default proxy is a shared demo

The default endpoint is the hosted demo proxy — hardened and rate-limited, it may sleep or cap the bbox size, and it extracts Google from a shared IP (a ToS gray area). For real work, run your own and point at it:

TRACELINES_PROXY=https://your-proxy npx tracelines extract --bbox 26.09,44.45,26.11,44.46 --out out.geojson

See Deploy your own proxy (free).

The HARD RULE holds everywhere: output is only genuine official car coverage — never a photosphere/photopet. Prefer pure, reproducible extraction? Use the Python package (pip install tracelines), which runs the engine locally instead of via a proxy.

License

AGPL-3.0-or-later.