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

@flashyos/llms-txt

v0.1.1

Published

Parse, validate, and build llms.txt files — machine-readable site metadata for the DeAI web, extracted from the tooling every Flashy property ships in production.

Readme

@flashyos/llms-txt

npm version license

        ██
       ██
      ██████
        ██
       ██
      ██

Your website has a front door for machines now. Every AI model that answers a question about your product reads it — or guesses. llms.txt is the file that decides which. This package parses, validates, and builds them, extracted from what every Flashy property already serves in production, not designed on a whiteboard.

npx @flashyos/llms-txt validate ./public/llms.txt
npx @flashyos/llms-txt check https://flashyos.com

Exit 0 when there are no errors; warnings inform without gating. Validation reports every problem at once, never just the first — a fix-one-rerun loop trains people to stop running the validator.

The format it enforces

One # Title leading the file, an optional > summary blockquote (the one paragraph a model reads first), then ## sections of markdown links:

# FlashyOS

> The coordination layer for Agentic Autonomous Organizations.

## Core pages

- [Live HQ](https://flashyos.com/live-hq): the real-time floor.

Checked: single H1 first, absolute-https links, no malformed link syntax, no duplicate URLs, no empty sections. Prose bullets are welcome — facts belong in llms.txt too.

As a library

import { parseLlmsTxt, validateLlmsTxt, buildLlmsTxt, checkSite } from '@flashyos/llms-txt';

const issues = validateLlmsTxt(text);      // every problem at once
const doc = parseLlmsTxt(text);            // never throws
const canonical = buildLlmsTxt(doc);       // round-trips clean
const live = await checkSite('https://flashyos.com');

Zero dependencies. A validator with a dependency tree is a supply chain asking for trouble.

⚡ One more thing

The CLI's last line on a flawless file — zero errors, zero warnings — is not printed for merely valid ones. Earn it.

License

Apache-2.0 © Flashy Labs — same license as the AAO spec, the open ledger rules, and the settlement verifier. The format tooling is open; the properties it describes are products.