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

imagelato

v1.2.0

Published

imagelato cli to manage projects, batches, and templates

Readme

imagelato

Command-line access to your image-delivery data on app.imagelato.com: projects, processed image batches with their resized and reformatted variants, and the deterministic resize/reformat templates that configure processing.

Install

npm install -g imagelato   # global install
npx imagelato --help       # or run without installing

Requires Node.js 18 or newer.

Quick start

imagelato login            # browser or API-key login
imagelato projects list    # your projects with their ids
imagelato batches list --projectId 64a1f2c9e4b0a1b2c3d4e5f6
Found 2 project(s):
1. marketing-site (64a1f2c9e4b0a1b2c3d4e5f6)
2. product-shots (64a1f2c9e4b0a1b2c3d4e5f7)

Signing up

No account yet? Create one from the terminal — the generated password prints exactly once, and the session is stored so every other command works immediately:

imagelato signup --email [email protected] --json

Authentication

Two ways in for an existing account; both store credentials in ~/.imagelato/:

  • Browserimagelato login --browser starts a temporary localhost server, opens app.imagelato.com, and receives the session tokens on the redirect back. If the browser does not open, the login URL is printed so you can visit it by hand. Tokens refresh automatically when they expire.
  • API keyimagelato login --with-key prompts (masked) for an API key secret and verifies it with one authenticated call before storing it. Create keys on app.imagelato.com under your project's API keys; new keys default to read-only scopes, so widen the key there before using write commands. The secret is never accepted as a command-line argument.

imagelato login with no flag asks which method to use. imagelato logout clears everything stored.

Headless environments can skip login entirely by exporting the key:

export IMAGELATO_API_KEY=<key secret>   # read at request time

A stored login session always wins over a stored or exported API key, so a globally-exported IMAGELATO_API_KEY never changes which account an interactive session talks to.

Without a terminal, a command with no credentials fails immediately with exit code 1 and login instructions on stderr — the CLI never opens a browser from a non-interactive environment. In an interactive terminal, a command run without credentials still opens the browser login itself.

Commands

Every resource supports three read modes:

  • list prints one summary line per record.
  • get prints every field — pass an id for one record, omit it for the whole array.
  • read prints one record formatted for the terminal.

Every subcommand also accepts --json: strict, parseable JSON on stdout, no color. Mutations print a small { "ok": true, "id": "…", "name": "…" } result. Failures go to stderr with exit code 1 — as a single JSON line in --json mode.

Projects and templates resolve by id or name; batches only by id.

Session

imagelato signup --email [email protected]   # create an account and log in
imagelato login              # choose browser or API key interactively
imagelato login --browser    # browser flow; tokens land in ~/.imagelato/
imagelato login --with-key   # masked prompt for an API key secret
imagelato logout             # clear the stored session and key

Projects

imagelato projects list [--json]                    # name and id per project
imagelato projects get [projectIdOrName] [--json]   # every field; omit the id for all projects
imagelato projects read <projectIdOrName> [--json]  # formatted view: locales, timestamps
imagelato projects create <name> [--json]           # create a project

Batches

A batch is the result of processing one image: the original plus every resized/reformatted variant and its URL. Batches are created by the Imagelato API when an image is processed — the CLI reads them.

imagelato batches list [--projectId <id>] [-n 20] [--json]         # most recent
imagelato batches get [batchId] [--projectId <id>] [-n 20] [--json]
imagelato batches read <batchId> [--json]                # variants, formats, sizes, URLs

Templates

A template is a reusable preset: the output formats and pixel widths future processing should produce. Formats are from jpg, png, webp, gif, svg; sizes are pixel widths.

imagelato templates list [--projectId <id>] [--json]
imagelato templates get [templateIdOrName] [--projectId <id>] [--json]
imagelato templates read <templateIdOrName> [--json]
imagelato templates add <name> --projectId <id> --formats jpg,webp --sizes 512,256,128,64
imagelato templates update <templateIdOrName> [--name <new>] [--formats ...] [--sizes ...]

templates add defaults to formats jpg,webp and sizes 512,256,128,64 when the flags are omitted, and requires a project id (flag or configuration file). Adding the same name twice creates two templates, so check templates list first. templates update replaces only the fields you pass.

Schema

imagelato schema                  # the whole command tree as JSON
imagelato schema templates add    # one command path only

Prints every command, option, argument, and default as parseable JSON — the machine-readable equivalent of --help, for agents and tooling.

Skills

imagelato skills list             # names and descriptions of the bundled agent guides
imagelato skills get imagelato    # print a bundled SKILL.md to stdout

Configuration

An imagelato.json in the working directory (or any subdirectory — the CLI scans downward from where it runs) supplies the default --projectId:

{ "projectId": "64a1f2c9e4b0a1b2c3d4e5f6" }

IMAGELATO_API_URL overrides the API endpoint (default https://api.imagelato.com) and IMAGELATO_APP_URL the login page — only needed against a non-production deployment.

Usage with AI agents

Install the Imagelato agent skills — imagelato (this CLI) and image-asset-workflow (the MCP-based delivery-audit workflow) — for Claude Code, Cursor, Codex, and any other agent that supports the Skills standard:

npx skills add imagelato/skills

The same guides ship inside the npm package, version-matched to the installed CLI:

imagelato skills list             # what is bundled
imagelato skills get imagelato    # the CLI guide matching this version

Or paste this into your AGENTS.md / CLAUDE.md:

## Image delivery

Use the `imagelato` CLI for image-delivery data: projects, processed batches
with their CDN variants, and resize/reformat templates. Run
`npx imagelato skills get imagelato` for the full guide, and
`imagelato schema` for the command tree as JSON. Add `--json` to any data
command for parseable output. Authenticate once with `imagelato login`, or
export `IMAGELATO_API_KEY` in headless environments.

Prefer a connector? The Imagelato MCP server at https://mcp.imagelato.com/mcp exposes the same data as tools for Claude, ChatGPT, and any MCP-capable host — see imagelato.com/developers.

License

Apache-2.0