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

@plico-ai/cli

v0.1.0

Published

The plico command line: validate, run, eval, readiness and serve with Studio

Readme

@plico-ai/cli

CLI entrypoints for validating Plico projects and running the deterministic dry runtime.

Commands

  • plico validate [path]
  • plico validate --json [path]
  • plico run --dry [path]
  • plico run --dry --json [path]
  • plico run --dry --script <file> [path]
  • plico cancel <runId> [--db <path>] [--json] [path]

plico validate keeps its current behavior. plico run is dry-run only in this release and uses the local runtime package for deterministic instruction composition, tool discovery, scripted tool execution, and approval blocking.

Durable runs

plico run --dry --persist resumes eligible interrupted runs in the selected database as it starts the requested run. It waits for each recovered execution to finish or reach a wait, reports recovery results on stderr, and uses the requested run's exit code. A waiting run needs a running host or a later persistent start to continue. plico serve adopts eligible runs at startup as well.

Set the optional host execution lease in plico.config.ts:

export default {
  schemaVersion: 1,
  name: "my-agent",
  execution: { leaseMs: 30_000 },
} as const;

The lease defaults to 30,000 ms and must be a positive integer. The host's setting applies to every run it recovers from its database. A short lease increases the chance that a stalled step runs again; side-effecting tools should use their idempotency key.

plico cancel <runId> [path] requests durable cancellation of a persisted run. The run's worker records the terminal cancellation event; if no worker is active, the next recovery pass finalizes it. --db <path> selects a non-default database and --json prints the cancellation result.