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

@tjalve/aie

v0.1.2

Published

AI Executor - autonomous GitHub issue execution for agentic development.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tjalve.npmtjalve.npm

Keywords

cligithubissuesautomationagentexecutor

Readme

@tjalve/aie

AI Executor — autonomous GitHub issue execution for agentic development.

Installation

Executor follows strict supply-chain policy.

Recommended (pinned, no lifecycle scripts):

pnpm install --frozen-lockfile --ignore-scripts
# or for one-off:
pnpm add @tjalve/[email protected] --ignore-scripts --save-exact

Do not use pnpm add @tjalve/aie@latest as the preferred path.

The package has no preinstall, install, or postinstall scripts.

Usage

aie --version
aie --help

Initialize a repository after installing the package:

aie init . --dry-run
aie init . --defaults --yes

Check repository readiness before starting work:

aie doctor
aie schema --json

Migration

Repositories that already have copied issue-workflow helpers can inspect and migrate to package-backed Executor commands without changing files first:

aie migrate map
aie migrate legacy
aie migrate legacy --dry-run
aie migrate legacy --dry-run --json

aie migrate legacy --dry-run shows detected legacy paths, instruction references that can be updated, compatibility wrappers that could be installed, cleanup candidates, preserved files, conflicts, required confirmations, and the next recommended command. Review that plan before applying any local file changes.

For a full adoption guide, see docs/migration.md.

Apply only the specific migration action you intend:

aie migrate legacy --apply --dry-run
aie migrate legacy --apply
aie migrate legacy --install-wrappers --dry-run
aie migrate legacy --install-wrappers --apply
aie migrate legacy --cleanup --dry-run
aie migrate legacy --cleanup --apply

Compatibility wrappers are temporary shims for repositories whose instructions still call old helper paths. Cleanup removes only known legacy helper files unless exact paths are selected and reviewed with the documented force behavior. After any apply run, review the git diff, run the configured checks, and commit only intentional source and documentation changes.

After migration, use the normal autonomous issue cycle:

aie queue
aie start next --dry-run
aie start next
aie doctor

Requirements

  • Node.js 24 LTS or newer
  • git
  • GitHub CLI gh

Design

See docs/spec.md for the functional requirements.