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

@assemblyline/al-orc

v0.4.1

Published

Assembly Line Orchestrator client + al-orc CLI (2-in-1): push lines and stations, run them, read work records.

Readme

@assemblyline/al-orc

The Assembly Line Orchestrator's client + al-orc CLI — a 2-in-1: import the client in code, or use the CLI to push lines and stations, run them, and read work records.

npm install -g @assemblyline/al-orc
al-orc login                                   # pick orgs in the browser; one profile per org
al-orc status                                  # org and key the profile belongs to
al-orc lines push --all && al-orc stations push --all   # from a factory repo root
al-orc stations run EX0
al-orc work-records list --station EX0

al-orc login opens the Orchestrator's approve page (over SSH, add --no-browser and open the printed link on any device). Orgs you already have a profile for show as connected; the current profile changes only when there was none. To add a key by hand instead: al-orc config profiles add acme --api-key <key> --api-secret <secret>.

Profiles live in ~/.al/al-orc/config.yml (mode 0600; override the folder with AL_ORC_CONFIG_DIR). The CLI never reads .env.

Library

import { alOrc } from '@assemblyline/al-orc';

const orc = alOrc({ api_key, api_secret });   // api_url optional (defaults to the hosted origin)
const { data: stations } = await orc.stations.list({ tag: 'daily' });
const station = await orc.stations.get(id);                       // unwrapped record
const { work_record_id } = await orc.stations.run(id, { overrides: { dry_run: true } });
await orc.workRecords.cancel(wrId);

Credentials are explicit — the client never reads process.env. Code serving several orgs constructs one client per org: alOrc(orgACreds).

Namespaces

| Namespace | Methods | |---|---| | orc.lines | list · getAll · get · create · update · delete — a line owns the location its stations run at | | orc.stations | list · getAll · get · create · update · delete · archive · unarchive · run · getTags · setTags | | orc.workRecords | list · getAll · get · activity · cancel · getTags · setTags | | orc.tags | list · create · update · delete · resolveNames · ensure | | orc.supportingDocs | get · downloadStream | | orc.factorySessions | list · getAll · get — one row per factory session start | | orc.me() | the org and API key the credentials belong to | | orc.checkConnection() | credentials check via me; never throws and never claims work |

Return shapes: single-record ops return the unwrapped record; list returns { data, page_context }; getAll returns a flat array.

Endpoint contract

Station routes live under /api/v1/stations/*; work records filter by ?station=. Every endpoint is defined exactly once, in src/resources/ — the CLI and the library both call it, so they can't drift.

Output conventions

Every command's terminal output follows these. They were implicit for a long time and drifted — format.js is copy-pasted across six sibling CLIs and each copy diverged — so they are written down here and covered by tests/cli/format.test.js. Use the src/cli/utils/format.js helpers rather than formatting inline; that is what keeps al-orc and al-control agreeing.

Timestamps — always formatDate(), never toISOString() or a raw Date. Output is the operator's local timezone, because everything these get compared against (pm2 logs, file mtimes, al-control output) is local. The orchestrator returns UTC, so printing it verbatim silently misread every timestamp by the local offset. Name the zone once per table or block via localTzLabel() in the column header — CREATED (${localTzLabel()}) — never per row. Durations use formatDuration().

Empty values — the em-dash '—', never '-', 'N/A' or blank. formatDate, formatDuration and truncate already return it, so || '—' is only needed for plain fields.

Free text — truncate(value, max) for anything unbounded (errors, titles, descriptions). It collapses whitespace first: a newline inside an error would otherwise break the table's alignment.

Tables — formatTable(headers, rows); pass no options object. Headers are UPPERCASE. Prefer the columns an operator needs to act (what failed, how long, who triggered it) over the minimum that identifies a row.

Lists — print the table, a blank line, then Total: N <things>. Follow it with formatPaginationHint(page_context), which is silent on a single page: Total: counts the rows returned, so without the hint a truncated page reads as the whole set. Empty results print No <things> found (no trailing period) and return early. --json prints the raw array, before the empty check, and is never decorated.

Detail views — formatHeader/formatSection for structure, formatField(label, value, 14) for fields; 14 is the shared label width. Order: identity, then timestamps, then nested sections. A nested section's own empty case does take a period (No tasks.), unlike a top-level list.

Advisory lines — prefix ! and indent continuations by three spaces, after a blank line. Say what to do about it, not just what is wrong.

Scripts

npm test         # jest (mocked fetch)
npm run typecheck  # tsc -p jsconfig.json  → 0 errors

License

Apache-2.0