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

@aspectlylabs/mikka

v0.0.670

Published

Local Mikka daemon: runs agents through the user's own CLIs

Readme

Mikka daemon

The daemon connects your computer to Mikka and runs threads with its own pinned Claude Code or Codex, installed when needed. Cursor is available on runners that report support for its adapter. Node.js 22 or newer and Git are required. Runs use the selected subscription or model credentials. Repository setup uses the task's authorized GitHub credential or existing machine Git credentials.

On Linux the agent sandbox also needs bwrap, socat and rg. No root is required: on Debian and Ubuntu the daemon fetches any that are missing from the machine's signed apt sources into its data directory. On other distributions, install them with the system package manager and the daemon picks them up by itself. Settings > Devices names anything it could not resolve.

The published @aspectlylabs/mikka package contains the mikka command and its daemon subcommands. The workspace package has private: true. pnpm --filter @mikka/daemon build produces the package with the private protocol bundled. The release workflow uses npm trusted publishing and verifies the published registry metadata.

Install the public package and start the daemon.

npm install -g @aspectlylabs/mikka
mikka daemon login
mikka daemon

Login prints a browser confirmation link and a short code. The daemon saves a device credential, never the browser session. The default server is https://app.aspectlylabs.com/mikka. For a local or self-hosted server, use the full application URL (including its base path) in both commands:

mikka daemon login --server https://mikka.example.com/mikka
mikka daemon --server https://mikka.example.com/mikka

mikka daemon status reports an already running daemon. Ctrl+C shuts it down. Manual test setup can use mikka daemon login --token <device-token>; keep the token out of screenshots, logs and shell history.

For background operation, install a service after signing in:

mikka daemon service install --server https://app.aspectlylabs.com/mikka --device-type laptop

For public npm installations running under launchd or systemd, the server names a newer stable release in a heartbeat, command response or refused claim. The daemon installs that exact version when idle. A failed install keeps the running version, waits 5 minutes, then 30 minutes, then 2 hours before retrying that version, and is reported to the server by code. Running work drains before installation and restart. Installation runs in the background so heartbeats remain available. The service keeps its server, data directory and device identity. Foreground, development and embedded daemons do not update themselves.

Add --no-auto-update when installing the service to disable automatic updates. The setting is saved in the service definition. Manual updates remain available through Mikka. An installation failure does not request a restart. npm replaces the global package in place, so an interrupted installation has no automatic rollback.

Build a release package

pnpm --filter @mikka/daemon build
export MIKKA_DAEMON_DIST_DIR=/absolute/path/printed/by/the/build
pnpm --filter @mikka/daemon test:package
npm pack "$MIKKA_DAEMON_DIST_DIR"

Each build writes a new .retained-build-* directory in the source package. Existing builds remain intact. The package test requires that exact directory and retains its .retained-package-test-* installation, tarball and fixture index for inspection. The test daemon still performs its normal lifecycle cleanup inside the new dedicated fixture; previously retained resources are not part of that fixture.

No global tsx or separate @mikka/protocol package is needed. A push to main that changes the daemon, the protocol, shared config, the lockfile or the release scripts publishes through .github/workflows/publish-daemon.yml after daemon checks and the installed-package runtime test pass. The workflow uses npm trusted publishing and provenance; its npm trust configuration must authorize this exact repository and workflow filename.

CI stamps 0.0.<workflow run number + 1> into the source manifest before the build, so the npm package and runtime report the same version. Source commits keep their development version. Re-running a workflow keeps its version and skips publication if npm already records that version from the same commit. CI writes the commit SHA into the published manifest as gitHead; an existing version with absent or different commit metadata stops the release. After publication, CI reads npm metadata back and checks the commit SHA. If npm serves 404 while the published version becomes available, CI checks up to 31 times with 10-second waits. Exhausting that wait reports registry verification as incomplete; it does not claim that npm rejected publication. Releases queue without cancellation (up to GitHub's 100 pending-run limit). An older run can publish under its own build-<version> tag, preserving the newer latest version. Manual dispatch remains available on main and gets a new run version. Running local tests or builds does not publish anything.

test:package installs the actual tarball into a new directory with public registry dependencies, without workspace symlinks or install scripts. Plain Node then runs the installed CLI and bundled mock daemon through a real clone/worktree/verification/commit/push against a disposable local bare origin. It verifies the pushed file and preserves the personal checkout. The test logs the tarball digest; its control plane and model are explicit in-memory fixtures. This is not real Claude Code/Codex, native-helper, live GitHub App or production device-authorization acceptance.