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

@clanker-chain/identity-node-client

v0.0.1

Published

Node/TypeScript client for the Bun-based identity service in this repo.

Readme

identity-node-client

Node/TypeScript client for the Bun-based identity service in this repo.


Purpose

  • Manage Ed25519 keys for a bot under ~/.openclaw/keys/{bot_id}.key.
  • Talk to the identity service over HTTP:
    • init()verify only: ensures the operator and bot exist and this bot's public key is registered (no POSTs; operator must mint the bot first).
    • GET /v1/operators/{id}, GET /v1/bots/{id} for lookups.
  • Produce canonical Ed25519 signatures for identity-aware messages that match the bot-comms.md design.

This is intended to be wrapped in an OpenClaw skill/tool so agents can call identity_init and identity_sign without handling HTTP or key management directly.


Installation

From this repo:

cd identity-node-client
npm install
npm run build

You can then import the built library from dist/ or reference the TypeScript source in your own tooling.


Basic usage

import { IdentityClient, type IdentityMessageEnvelope } from "./dist/index.js";

const client = new IdentityClient({
  botId: "openclaw.france.prod-1",
  operatorId: "org.openclaw.pat",
  identityServiceUrl: "http://localhost:8080",
});

// One-time (idempotent) init on startup: verifies operator and bot exist and this bot's key is registered.
// The operator must have minted the bot (e.g. via identity-service CLI mint-bot) with this bot's public key first.
await client.init();

// Later, when sending a message:
const envelope: IdentityMessageEnvelope = {
  from: "france-bot",
  from_id: "openclaw.france.prod-1",
  operator_id: "org.openclaw.pat",
  to: "tooter-bot",
  to_id: "openclaw.tooter.prod-1",
  type: "coordination",
  subtype: "task-claim",
  timestamp: new Date().toISOString(),
  message_id: "uuid-here",
  correlation_id: undefined,
  body: {
    action: "claim_task",
    task_id: "task-123",
  },
};

const { signature, signature_scheme } = await client.signMessage(envelope);
const signedEnvelope = { ...envelope, signature, signature_scheme };

Environment variables

  • IDENTITY_SERVICE_URL — default base URL for the identity service (fallback: http://localhost:8080).
  • The identity service uses proof-based auth (signatures); no admin token is required for init or lookups.

Integration with OpenClaw skills (sketch)

In an OpenClaw workspace skill, you can wrap this client behind a tool like:

  • identity_init(bot_id, operator_id) — calls client.init().
  • identity_sign(envelope) — calls client.signMessage(envelope) and returns the signature to the agent.

That way, the agent never needs to know about HTTP details or key storage locations; it just invokes the skill’s tools.