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

pi-time-tracker

v0.2.3

Published

Private working-hours receipts for Pi, reconciled by a tested Bend accounting policy.

Vulnerabilities

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

Links

Git

Maintainers

ryanjoserbrosasryanjoserbrosas

Keywords

pi-package

Readme

pi-time-tracker

Automatic work tracking for Pi.

Track client work across projects, keep records local, and review your hours.

checks npm version Pi extension License: MIT

Built for working across client repos in Pi without remembering to start and stop a timer. Open Pi in a project's folder and work as usual; the tracker associates activity with that workspace so you can review your hours later.

Run

After installing, tracking starts automatically. In Pi:

/project report

Workspace reports go to exports/work-report.md. Keep exports/ out of Git. Hours are inferred from Pi activity, not confirmed billable time; review them before using them in a timesheet or invoice.

Why pi-time-tracker?

| | Capability | What it unlocks | | :-: | --- | --- | | ⏱️ | Automatic tracking | Infer work windows without managing a timer. | | 🔀 | No double-counting | Count overlapping sessions once; long idle gaps stay Unknown. | | 🔒 | Local records | Built-in SQLite; no external sync or automatic prompt/transcript capture. | | 📝 | Reviewable reports | Markdown drafts, optional outcome notes and a separate manual clock. |

How it fits

Pi activity → local SQLite and receipts → Markdown reports.

The extension observes activity inside Pi, including prompts, agent turns and tool events. It joins nearby activity into inferred work windows; long idle gaps stay Unknown. Leaving a session open does not turn its whole lifetime into work, and activity outside Pi is not observed.

Records stay on your machine, with no database server to set up. Workspace reports keep inferred work windows, measured agent activity and the optional manual session clock separate — they are different views, not hours to add together. See the architecture and development guide for details.

Install

Requires Node.js >=22.19.0 and a Pi 0.87.1-compatible host.

pi install npm:pi-time-tracker

Use --local to install for just the current project. Approve project trust when prompted, then use /reload in Pi. If switching from Git or a local checkout, remove the previous install first rather than loading both.

Usage

The folder name is the default client label. Set a name once and future sessions in that workspace inherit it; task labels apply to the current session:

/project set Coral   # optional client name; defaults to the folder name
/project task docs   # optional task for this session
/project report all  # report across tracked workspaces

Use /project status to check the current workspace, task and tracking settings. The all report covers inferred work windows across your tracked projects; manual session clocks and agent receipts stay in their workspace reports.

Documentation

License

MIT. Copyright © 2026 Ryan Brosas.

Powered by Coral Bricks.