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

@honeycrisp/folders

v0.1.1

Published

Folder-as-API: watched folders run declared local pipelines; results land beside the drop; every run is audited

Downloads

37

Readme

honeycrisp-folders

The filesystem is the interface. Watched folders run declared pipelines: drop a file in from any device that can reach the folder (iCloud Drive makes that every Apple device), and the result appears beside it. No app, no UI, no login.

Agents/
├── Shout/
│   ├── .pipeline.yaml        ← the folder documents itself
│   ├── hello.txt             ← you drop this
│   └── hello.txt.result.md   ← this appears
└── Wordcount/
    └── .pipeline.yaml

Pipeline definition

name: shout
description: uppercase any text file
steps:
  - name: read
    run: ["cat", "{input}"]     # argv array — never a shell string
  - name: shout
    run: ["tr", "a-z", "A-Z"]   # receives previous step's stdout on stdin
  • {input} = the dropped file's absolute path; {dir} = the pipeline folder.
  • Steps chain stdout → stdin; the last step's stdout becomes <name>.result.md, stamped with provenance.
  • A step that talks to the network must declare network: true — the folder's contract is inspectable before you drop anything in it, and the declaration lands in the audit row.

Failure is loud, silence is never the outcome

A failing step writes <name>.error.md beside the drop, in plain English: which step, what happened, what to do. Every run — success or failure — writes a row to the suite's shared audit DB.

Running

honeycrisp-folders ~/Library/Mobile\ Documents/com~apple~CloudDocs/Agents

For always-on operation, install the launchd template in launchd/ (instructions inside). iCloud dataless files are requested for download automatically (brctl download); processing starts when the bytes arrive.

Trust model (v1)

Anyone who can write a folder's .pipeline.yaml decides what runs on drops into that folder. Keep the watched root inside your own iCloud Drive (private by default) and treat shared folders as untrusted. Command allowlisting / pipeline pinning is on the roadmap.