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

aclade

v1.0.3

Published

Aclade — autonomous AI experts that do real work. `npx aclade` connects your machine to your Aclade team with a zero-trust local connector.

Readme

Aclade

Autonomous AI experts that do real work. Aclade rents you AI employees — a CTO who reviews code, an analyst who pulls data, a marketer who ships campaigns — and they can act on your own machine through a zero-trust local connector.

This package (aclade) is the front door: one command to connect this machine to your Aclade team.

Docs & examples: github.com/aclade-ai-expert/aclade-docs — CLI reference, Python SDK guide, architecture notes, and worked examples.

Quickstart

# 1. Get a connection token:  https://aclade.com  →  Settings → Local Agent
# 2. Connect this machine (installs & daemonizes automatically):
npx aclade connect --token <TOKEN>

# 3. Check it:
npx aclade status

Or install globally:

npm install -g aclade
aclade connect --token <TOKEN>

No Node.js on the machine? The portal's one-liner bootstraps a private Node for you (arguments after -- reach the installer, not curl):

curl -fsSL https://aclade.com/install.sh | bash -s -- --token <TOKEN>

Commands

| Command | What it does | |---|---| | aclade connect --token <T> | Starts (or replaces) the local agent daemon | | aclade connect --token <T> --workspace /path | Same, but the agent refuses to operate outside /path | | aclade status | Local agent state + live fleet as seen by aclade.com | | aclade stop | Stops the local agent | | aclade --version | Show versions |

Anything else is passed straight through to the aclade-agent connector.

Python

Prefer import aclade? The official Python SDK drives the same platform from code:

import aclade
team = aclade.Aclade(token="<TOKEN>")
for e in team.experts():
    print(e["name"], e["title"])
result = team.delegate(team.experts()[0], "Summarize our top 3 customer complaints")
print(result["run"]["report"])

Security model

  • Zero-trust polling. No inbound ports are opened. The agent polls aclade.com outward over HTTPS and nothing else.
  • Short-lived tokens. The connection token is a signed 12-hour session bound to your workspace. It can never be another tenant's, and it can never carry admin authority. Treat it like a password. The agent rotates it automatically in the final 90 minutes (proof-of-possession), so a running daemon stays connected without operator action.
  • Scoped file tools. --workspace /path confines the file tools (read, write, edit, list, glob, grep, index) to one directory. Be aware that execute_bash and schedule_cron are NOT confined by that scope — they run on your machine, which is the point of the connector.
  • The AI stays in the cloud. This package contains no LLM logic, weights, or reasoning loops. All intelligence runs on Aclade infrastructure; the agent is a thin, inspectable executor that does exactly what the platform instructs — and nothing it does not.
  • Set-and-forget. The agent self-updates through npm. Under a supervisor, start it with --foreground so the supervisor owns restarts (see the aclade-agent README); on servers, pm2 is the usual choice.

What runs where

┌─────────────────────────────┐         HTTPS polling (outbound only)        ┌──────────────────────────────┐
│  Your machine               │  ◄─────────────────────────────────────────►  │  aclade.com                 │
│                             │      tasks / results, 12h signed token       │                              │
│  aclade-agent (this pkg)    │                                              │  The harness: 409 roles ×    │
│  executes: bash, files,     │                                              │  personas, tools, RAG,      │
│  grep, browser, embeddings  │                                              │  metering — all server-side │
└─────────────────────────────┘                                              └──────────────────────────────┘

Troubleshooting

  • Logs: ~/.aclade-agent.log
  • Config: ~/.aclade-agent.json (contains your token — it's written 0600 for a reason)
  • Token expired? Issue a fresh one in the portal and re-run aclade connect --token <TOKEN> — the new daemon replaces the old one automatically.

Copyright © Aclade. Proprietary software (UNLICENSED), distributed exclusively for users of the Aclade platform. aclade.com