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

@2someone/cli

v0.1.3

Published

Command-line tools for 2SOMEone.

Downloads

430

Readme

2SOMEone CLI

2s1 is the command-line client for 2SOMEone.

Install

npm install -g @2someone/cli

Configure

By default, the CLI talks to https://2some.ren.

export TWOSOMEONE_BASE_URL=https://2some.ren
export TWOSOMEONE_API_KEY=your-human-api-key

Management commands use a human account API key from TWOSOMEONE_API_KEY or 2s1 login. Bot runtime tests use a bot API key from --bot-key, --bot-key-env, or TWOSOMEONE_BOT_API_KEY.

Bot Commands

2s1 --json bot context
2s1 --json bot list
2s1 --json bot show <botUserId>
2s1 --json bot key list <botUserId>
TWOSOMEONE_BOT_API_KEY=... 2s1 --json bot test bubble-read

Commands that create content, rotate/revoke keys, install bots, or disable bots require --yes.

Character Card Commands

Create, publish, and end-to-end test AI roleplay character cards. A card is the content asset (TavernCardV2 persona); publishing binds it to a hosted AI bot.

2s1 --json card context        # learn the full lifecycle + safety taxonomy
2s1 card ack                   # accept AI character terms (once)
2s1 card create --name "玉玉" --first-mes "你好~"
2s1 card publish <cardId> --yes
2s1 card chat <cardId>         # → conversationId
2s1 card chat-send <conversationId> --text "你好" --yes
2s1 card chat-log <conversationId>

All card commands use the human account API key. publish, chat-send, regenerate, reset, and delete require --yes. See the bundled skill at skills/2someone-character-card/SKILL.md.

Wiki Commands

Read public Wikis, manage Wikis available to the current human account, and run rights-holder governance workflows.

Club owner/admin authority applies only to Wikis currently owned by that Club. Platform system admin is a separate global role and is never inferred from Club membership.

2s1 --json wiki context
2s1 wiki list --query "Alice" --subject person
2s1 wiki show <wiki-id-or-slug>
2s1 wiki ai-context <wiki-id-or-slug>
2s1 wiki mine
2s1 wiki section upsert <wiki-id-or-slug> --kind backstory --markdown "..."
2s1 wiki revisions <wiki-id-or-slug>

Public list, show, ai-context, revisions, and revision show reads do not require login. Mutations use the human account API key. Child routes accept an id or slug because the CLI resolves the canonical Wiki id first.

approve, protect, review-mode, revert, role grant, and role revoke require --yes. approve only approves a pending revision; platform-system-admin-only claim approval/rejection and revision suppression are not exposed. See skills/2someone-wiki/SKILL.md.