#packageregistry
Live, measured metrics for the hashtag #packageregistry from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #packageregistry
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mas.to (Mastodon public tags API) · fetched 2026-10-02 16:02 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-02 16:02 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-02 16:02 UTCEverything below is measured over the latest 2 public posts (spanning ~5257 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1
Top of the latest posts
🥳 Behold, the "SwiftHive" - a revolutionary package registry that claims to speed up your builds by a whopping 10x! 🚀 Because, clearly, the world has been waiting for yet another tool to complicate its life with "immutable versions" and a
Node.js Toolbox An overview of what open source libraries are available for a given task grouped by category. #NodeJS #NPM #JavaScript #TypeScript #Programming #LibraryCatalog #PackageRegistry #OpenSource https://nodejstoolbox.com/
#packageregistry across platforms
every network with a public tag surfaceFollow #packageregistry straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/packageregistry