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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@engines-dev/forge

v0.2.2

Published

A CLI package for the Forge AI platform engineer that helps set up and manage development environments.

Readme

A CLI package for the Forge AI platform engineer that helps set up and manage development environments.

Installation

npm install -g @engines-dev/forge

Usage

forge [options]

The CLI runs Forge in a Docker container with your current directory mounted as the working environment.

The most likely option you'll want to use is --no-interactive which will start the agent and attempt to build a Docker container for a repo. You can also pass in -p "this is a Java monorepo" to pass more info in a prompt in the non interactive mode.

Environment Configuration

Forge looks for environment variables in the following order:

  1. --env-file=path/to/file (if specified)
  2. ./.env (current directory)
  3. $HOME/.env (home directory)

Required environment variables: ANTHROPIC_API_KEY=your_api_key_here

Features

  • Autonomous Setup: AI-driven development environment configuration
  • Docker Integration: Runs in isolated containers with Docker socket access
  • Output Management: Saves generated files to ./output directory

How It Works

The CLI script:

  1. Creates an ./output directory for generated files
  2. Runs the Forge Docker container (enginesdev/forge)
  3. Mounts your current directory as read-only (/host:ro)
  4. Provides workspace persistence via Docker volumes
  5. Loads environment variables from .env files

All generated content is saved to the local ./output folder for easy access.