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

@chronicle.app/apple-call-history

v0.5.0

Published

Chronicle plugin for extracting phone & FaceTime calls from Apple Call History (with a Timing.app supplement)

Readme

@chronicle.app/apple-call-history

Chronicle plugin that extracts phone & FaceTime calls from Apple Call History and folds them into the existing comms identity graph (iMessage/WhatsApp via phone/email + @me).

Source

~/Library/Application Support/CallHistoryDB/CallHistory.storedata (read-only) — the rich, per-record source (direction, number, duration, participants).

A call's CallSession is keyed by source: apple-call-history and sourceId = <call UUID> (ZUNIQUE_ID), and its CallAction by that session (result.sourceId). Apple's store has a rolling retention (~recent calls); the longer history that Apple prunes is relayed through Timing.app and lives in the timing-app plugin (-t calls), which emits the same apple-call-history + UUID identity so the two fold into one call.

The service (phone / FaceTime / VoIP) is not modeled yet (it needs cross-source action identity, since the shared key is Apple's UUID).

Frame

A call is shared co-presence, not a directed send, so participants live on :with, not :recipient:

CallAction   agent = initiator (when known)   object = CallSession   startTime/endTime
  CallSession  with = [participants other than @me]
  • Direction (ZORIGINATED): outgoing → agent: @me; incoming 1:1 → agent: the caller; incoming group → agent omitted.
  • Connected vs missed is derived from the span (missed ⇒ endTime == startTime).
  • Participants are Person keyed on phone (E.164) or email — folding into the iMessage/WhatsApp graph and @me.
  • Blocked/private numbers (empty address) carry no participant.

Usage

chronicle extract apple-call-history                          # Apple Call History (rich; type: calls)
chronicle extract apple-call-history --input /path/to/CallHistory.storedata --since 2025-01-01

Tests

Tests build a synthetic CallHistory.storedata and a synthetic AddressBook with node:sqlite, and pass the transformer an explicit iCloud account and a lookupContact over that AddressBook, so they never read the host's call history, contacts, or iCloud account.