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

@heysnap-ai/web

v0.1.0

Published

Agent-friendly web CLI: search, scrape, and agentic research over the open web. Routes through the local ank1015 cloud-server gateway.

Readme

@heysnap-ai/web

An agent-friendly CLI for working with the web — exposes search, scrape, and an agentic research command that produces a structured, cited markdown report. All traffic routes through the local ank1015 cloud-server gateway, so no third-party provider keys live on the machine.

npm install -g @heysnap-ai/web
web --help

Quick start

# Required env, on the machine container:
export CLOUD_SERVER_PUBLIC_URL=http://host.docker.internal:4100
export ANK1015_MACHINE_TOKEN_FILE=/opt/ank1015/machine-token

# Search the web
web search "claude opus 4.7" -n 10

# Scrape a single page
web scrape https://firecrawl.dev -q > page.md

# Agentic research → saves a markdown report under /tmp/web-research/
web research "state of small LLMs in 2026"

Commands

| Command | What it does | |---|---| | web search | Web search via the gateway's Firecrawl route. Titles, URLs, snippets. Operators like site:, "...", -term, filetype: pass through. | | web scrape | Fetch a single URL as markdown / HTML / links / screenshot. Large pages auto-saved to a temp file with only a preview printed inline. | | web research | Agentic loop: searches, scrapes, and synthesizes a structured markdown report. Per-scrape compression by a small extractor model lets it span ~10–15 sources. |

Run any command with --help for the full reference, or see docs/:

Conventions

  • Data goes to stdout, diagnostics to stderr — pipes stay clean.
  • Output auto-switches: TTY → pretty, pipe → JSON. Override with --json / --pretty / -q.
  • Exit codes: 0 ok · 1 usage/validation · 2 API/network · 3 research-specific "no report produced".

Auth

Two env vars, no provider keys:

CLOUD_SERVER_PUBLIC_URL=http://host.docker.internal:4100
ANK1015_MACHINE_TOKEN_FILE=/opt/ank1015/machine-token

ANK1015_MACHINE_TOKEN_FILE is a path to a file containing the bearer token (per the Docker-secret _FILE convention). The CLI reads and trims it at startup. The gateway routes Firecrawl traffic to ${CLOUD_SERVER_PUBLIC_URL}/firecrawl and OpenAI Responses-API traffic to ${CLOUD_SERVER_PUBLIC_URL}/llm/openai/v1.

Development

npm install
npm run dev        # tsx watch
npm run typecheck
npm test           # unit tests (no network)
npm run build      # → dist/

Integration tests spawn the built CLI as a subprocess. Set the gateway env above to run live tests:

npm run test:integration

License

UNLICENSED.