How we pick and verify

How Pi Index chooses listings, pins guide reviews to a version and commit, refreshes GitHub stars and npm downloads, and treats the optional badge.

What gets listed

This is a curated list, not a mirror of pi.dev/packages. Entries are grouped by what they do. Projects with a GitHub repository or their own documentation are preferred. The list draws on pi.dev/packages, GitHub, npm, and other public community sources.

An npm: install command does not make a package part of official Pi. Something is described as official Pi only when its publisher and source repository support that. Projects stay under their authors’ copyright. The list itself is CC0.

How a guide is checked

A guide is not the directory line. Each project on a guide is marked “Source / documentation reviewed” or “Tested”, with the date, a version, and a commit or other revision, plus links to the files that were read. Features, performance, and savings that are not marked tested are not measurements by this site.

Topic pages name the day they were compiled. The Pi Durable topic was compiled on 2026-10-07: it kept projects whose non-test source imports @earendil-works/pi-durable, reviewed each at a pinned commit, and did not install them. The Jev topic was reviewed on 2026-09-22 from source and docs, without paid API calls.

Stars and downloads

GitHub stars and npm downloads are refreshed by a GitHub Actions workflow every Monday at 02:17 UTC. It can also be run by hand. The download figure is the sum of the seven days ending the day before that run, and the percent change compares those days with the seven before them. The home page prints the snapshot date.

When a request fails and an older figure exists, that figure is kept. A project that has never returned a number shows nothing. A missing figure is not a zero.

The badge

Listing costs nothing, and there is no application form. The “Listed on Pi Index” badge in the README is optional. Adding it does not change whether a project is listed, how it is listed, or whether a guide recommends it.

Corrections

If a description, install command, or review is wrong, open a GitHub issue. Who maintains the site is on About.

Open an issue ↗