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

@aioschema/cli

v0.5.12

Published

AIOSchema v0.5.5 — command-line tool for generating and verifying provenance manifests.

Downloads

103

Readme

@aioschema/cli

AIOSchema v0.5.5 — Command-line tool for generating and verifying provenance manifests.


Install

npm install -g @aioschema/cli

Note: You can also run directly from source without installing:

git clone https://github.com/aioschema/aioschema.git
cd aioschema/cli
node cli.js --help

Usage

# Generate a manifest for any file
aioschema generate myfile.pdf

# Generate with SHA-384
aioschema generate myfile.pdf --algorithm sha384

# Generate with your creator ID
aioschema generate myfile.pdf --creator-id ed25519-fp-ebc64203390ddefc442ade9038e1ae18

# Generate with extension fields
aioschema generate article.md \
  --creator-id ed25519-fp-ebc64203390ddefc442ade9038e1ae18 \
  --ext asset_name=article.md \
  --ext asset_type=document \
  --ext description="My article about digital provenance"

# Verify a file against its manifest
aioschema verify myfile.pdf myfile.pdf.aios.json

# Help
aioschema --help

# Version
aioschema --version

What it produces

Running aioschema generate writes a .aios.json manifest alongside your file:

myfile.pdf
myfile.pdf.aios.json   ← manifest

The manifest cryptographically describes your file — what it is, when it existed, and who created it. Verifiable forever by any conforming AIOSchema implementation.


Extension fields

Use --ext key=value to add metadata to the manifest's extensions block. The flag is repeatable — pass it once per field:

aioschema generate article.md \
  --creator-id ed25519-fp-ebc64203390ddefc442ade9038e1ae18 \
  --ext asset_name=article.md \
  --ext asset_type=document \
  --ext description="LinkedIn article: Understanding Digital Provenance"

Extension fields are informational and do not affect Core Block integrity or Level 1 verification.


Creator ID

The --creator-id flag is optional but important.

Without it: a new unique ID is auto-generated every time you run generate. Each file gets a different creator ID — there is no link between them. This is fine for one-off provenance but means you cannot prove that two files came from the same author.

With it: every manifest you generate carries the same identity. Anyone verifying your files can confirm they all came from the same creator. This is the recommended approach for anyone publishing content, releasing software, or establishing a consistent authorship record.

Your creator ID is derived from your Ed25519 public key and has the format:

ed25519-fp-<64 hex characters>

Generate it once, store it safely, and use it for all your files. See the implementation docs for how to generate a keypair and derive your creator ID.


Library

For programmatic use, see @aioschema/js.


License

Apache 2.0. See LICENSE.md.
Specification: CC-BY 4.0 — aioschema.org