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

@linktogo/maggie-ci-status

v1.2.0

Published

CI status payloads for maggie: build them from a GitHub Actions run, validate them, and fold them into per-repo, per-contributor state.

Downloads

205

Readme

@linktogo/maggie-ci-status

CI status payloads for maggie: build one from a GitHub Actions run, validate one read back from disk, and fold a set of them into per-repo, per-contributor state.

Pure functions only — no I/O, no git, no network. The composite action uses it to produce a status file; the board server uses it to consume one.

import { buildUpdate, parseUpdate, buildState, normalizeState } from '@linktogo/maggie-ci-status';

// In a GitHub Actions runner: build the payload from either trigger context
const update = buildUpdate(process.env, event, new Date().toISOString());

// Reading it back: validate against the path it was found at
const parsed = parseUpdate(raw, { login: 'fabien', repo: 'example-api' });
if (!parsed.ok) console.warn(parsed.reason);

// Fold many into { repos: { <repo>: { users: { <login>: entry } } } }
const state = buildState(entries, new Date().toISOString());

normalizeState('completed', 'timed_out'); // → 'failure'

| Export | Purpose | |---|---| | buildUpdate(env, event, now) | Build a payload from a workflow_run event or from an in-job step context. | | parseUpdate(raw, { login, repo }) | Validate one status file, including that it matches the path it sits at. Never throws. | | buildState(entries, now) | Fold { login, repo, update } triples into per-repo, per-contributor state. | | normalizeState(status, conclusion) | Map a run to success, failure, running or neutral. | | rankState(state) | Total order used to sort worst-first and to aggregate. | | redactToken(message, token) | Replace a token with *** in an error message. | | statusRepoUrl(statusRepo, token) | Build the clone URL for owner/name, passing a full URL through unchanged. |

See CI status for how the pieces fit together.