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

allfy

v0.7.4

Published

Alfred CLI

Readme

🤖 Alfred

The butler for the CLI

Limitations

  • Currently only supports MacOS
  • Only supports .zprofile for now

Getting Started

  1. Clone the repository
  2. Run bun install
  3. Create commands.json in the root directory : echo "[]" > commands.json
  4. Run bun compile
  5. Try running alfred in the terminal (e.g alfred hello)

Command Schema

AlfredCommandSchema

The schema for an Alfred command is as follows:

interface AlfredCommandSchema {
    name: string; // The name of the command
    description: string; // A brief description of the command
    command: {
        dir?: string; // Optional directory where the command should be executed
        cmd: string; // The command to execute
    };
    config?: {
        confirm?: boolean; // Optional flag to require confirmation before execution
    };
    extends?: string; // Optional name of a command to extend
    options?: {
        flags: string; // Command line flags (e.g., "-n, --name [name]")
        description: string; // Description of what the option does
        required?: boolean; // Whether the option is required
        defaultValue?: any; // Default value for the option
        envVar?: string; // Environment variable to use for the option
        choices?: string[]; // Array of string choices for the option
        type?: "number" | "string" | "boolean" | "url" | "path"; // Type of the option
    }[];
}

Examples

Example 1: Basic Command

{
    "name": "hello",
    "description": "Prints hello world",
    "command": {
        "cmd": "echo 'Hello, World!'"
    }
}

Example 2: Command with Options

{
    "name": "greet",
    "description": "Greets the user",
    "command": {
        "cmd": "echo 'Hello, ${name}!'"
    },
    "options": [
        {
            "flags": "--name [name]",
            "description": "Name of the user",
            "type": "string",
            "defaultValue": "User"
        }
    ]
}

Example 3: Extending a Command

{
    "name": "list",
    "description": "List files",
    "command": {
        "cmd": "ls"
    }
},
{    "name": "list:all",
    "extends": "list",
    "command": {
        "cmd": "{super} -a"
    }
}

An extended command doesn't need to redefine commands, and can simply redefine options.

Options

  • flags: Command line flags (e.g., --name [name]).
  • description: Description of the option.
  • required: Whether the option is required.
  • defaultValue: Default value for the option.
  • envVar: Environment variable for the option.
  • choices: Array of string choices.
  • type: Type of the option (number, string, boolean, url, path).

Configuration

  • confirm: Whether confirmation is needed before executing the command.