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

alys-akusa

v0.1.22

Published

Alys local CLI runtime for autonomous AI data preparation.

Readme

Alys CLI

Alys is the terminal-native runtime for autonomous AI data preparation.

npm install -g alys-akusa
alys prepare ./company-docs

Or run without installing:

npx alys-akusa prepare ./company-docs
npx alys-akusa audit ./knowledge-base
npx alys-akusa simulate-rag ./knowledge-base
npx alys-akusa improve ./knowledge-base
npx alys-akusa benchmark ./knowledge-base
npx alys-akusa ingest ./knowledge-base
npx alys-akusa finetune-ready ./support-tickets

Alys turns messy local knowledge into OpenAI fine-tuning JSONL, Anthropic instruction records, RAG chunks, QA datasets, eval datasets, embeddings-ready corpora, manifests, source lists, and AI readiness reports.

What It Does

messy knowledge
  -> ingestion
  -> parsing
  -> chunking
  -> deduplication
  -> semantic grouping
  -> grounding
  -> evaluation
  -> AI-ready exports

Local preparation writes artifacts under ~/Alys/prepared/{run_id} and does not require users to bring model API keys. Retrieval simulation writes retrieval-simulation.json and retrieval-simulation.md with hit rate, overlap failures, weak boundaries, unsupported-answer risk, and hallucination risk. Improve writes a safe optimized copy under ~/Alys/improved/{run_id} with improved-rag-chunks.jsonl, cleaned-corpus.md, and an improvement report. It does not mutate original source files. Benchmark writes knowledge-benchmark.json and knowledge-benchmark.md under ~/Alys/benchmarks/{run_id} to compare original vs improved retrieval behavior, answer support, grounding, hallucination risk, and regressions.

Local Development

Do not publish to npm for normal testing. Use the repo CLI directly first:

pnpm install
pnpm alys -- audit ./knowledge-base --yes
pnpm alys -- simulate-rag ./knowledge-base --queries 12 --top-k 5 --yes
pnpm alys -- improve ./knowledge-base --yes
pnpm alys -- benchmark ./knowledge-base --queries 16 --top-k 5 --yes
pnpm alys -- prepare ./docs --profile all --yes
pnpm alys -- ingest ./knowledge-base --profile rag,embeddings,eval --yes
pnpm alys -- finetune-ready ./tickets --profile openai,anthropic,qa --yes

Recommended pre-publish loop:

pnpm cli:test
pnpm cli:smoke:local
pnpm cli:pack

pnpm cli:smoke:local does not call the hosted generation API. It audits the repo docs folder and writes disposable artifacts to ./.alys-test.

Use the API smoke only when you explicitly want to test the live hosted generation path with a tiny run:

pnpm cli:smoke:api

Only after those pass should you publish:

cd apps/cli
npm publish --access public