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

@aionis/create

v0.2.10

Published

One-command installer for Aionis Runtime and agent integration packages.

Downloads

2,748

Readme

@aionis/create

One-command installer for Aionis Runtime, SDK, MCP bridge, AIFS, and optional Claude Code lifecycle hooks.

Docs: https://docs.aionis.work/developer-platform/start/install

Source repositories:

Run:

npx @aionis/create@latest

For the guided product setup flow, use the top-level CLI instead:

npx aionis setup

That command prompts for provider and integration choices, collects optional API keys with hidden terminal input, then delegates the install to this package.

The default run installs Aionis and starts the no-key first-value demo. It shows the Memory Firewall blocking failed and stale memory before you configure an embedding provider.

Run the full SDK quickstart with OpenAI-compatible embeddings:

OPENAI_API_KEY="your-key" npx @aionis/create@latest --provider openai --quickstart sdk

Install without running any quickstart:

npx @aionis/create@latest my-aionis --skip-quickstart

Install Runtime into a side directory and onboard Claude Code globally:

npx @aionis/create@latest .aionis-runtime --with-claude-code

This writes PORT=3101 into .aionis-runtime/.env, matching the Claude Code plugin default http://127.0.0.1:3101. Start Runtime with:

cd .aionis-runtime
npm run -s lite:start

Install Runtime and include AIFS file-surface setup commands in the completion output:

npx @aionis/create@latest my-aionis --with-aifs

@aionis/create does not add AIFS to the Runtime package.json. Run AIFS from the agent project that should contain .aionis/:

npx @aionis/aifs@latest init --base-url http://127.0.0.1:3001 --scope my-project
npx @aionis/aifs@latest doctor --base-url http://127.0.0.1:3001 --scope my-project
npx @aionis/aifs@latest refresh --base-url http://127.0.0.1:3001 --scope my-project

The installer clones the Runtime repo, installs dependencies, writes .env, runs the Runtime build check, then optionally runs a quickstart and Claude Code onboarding. Use @aionis/sdk for application integration, @aionis/mcp for MCP clients, @aionis/aifs for .aionis/ workspace files, and @aionis/claude-code for Claude Code lifecycle integration.

If no embedding key is detected, the installer writes EMBEDDING_PROVIDER=none so the local Runtime can start immediately. That no-key mode is enough for the first-value demo, MCP wiring, execution-memory smoke tests, and Memory Firewall candidate governance. Configure semantic recall later by setting EMBEDDING_PROVIDER=openai plus OPENAI_API_KEY, or EMBEDDING_PROVIDER=minimax plus MINIMAX_API_KEY, in the generated .env.

Common first runs:

OPENAI_API_KEY="your-key" npx @aionis/create@latest --provider openai --quickstart multi-agent

After install, pick the integration path: