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

timeline-pulse

v0.1.1

Published

MCP server + public atlas of timeline-shift folklore, Mandela Effect reports, and collider-era myth — every claim labeled, every source graded. A cultural archive, not a proof engine. Built while the LHC sleeps (LS3, 2026–2030).

Readme

Timeline Pulse ◉

The machine went quiet. The stories didn't.

Timeline Pulse is an open-source MCP server and interactive atlas of timeline-shift folklore, Mandela Effect reports, collider-era myths, and symbolic reality stories — every claim labeled, every source graded.

On 2026-06-29 the LHC was switched off for Long Shutdown 3, and won't collide again until ~2030 (CERN). Communities tell stories around machines like this. This project files those stories properly: official facts on one shelf (always cited), beliefs and symbols on another (always labeled), and tools so humans and AI agents can explore both without confusing them.

Timeline Pulse treats its material as cultural, symbolic, experiential, and speculative storytelling. It does not claim that CERN, the LHC, particle physics, timelines, or Mandela Effects prove supernatural or physical timeline manipulation.

  • Site: https://timeline-pulse.vercel.app
  • Package: timeline-pulse on npm — no keys, no backend, read-only
  • Built end-to-end with Claude (Claude Code + Claude in the browser designed, documented, and implemented this repo), reviewed by a human

Use it as an MCP server

{
  "mcpServers": {
    "timeline-pulse": {
      "command": "npx",
      "args": ["-y", "timeline-pulse"]
    }
  }
}

The seed corpus ships inside the package: 20 reports, 17 motifs (24 co-occurrence edges), 6 Mandela catalog items, 8 story threads, 9 timeline events with 5 officially-sourced CERN anchors.

MCP tools

| Tool | Purpose | | --- | --- | | timeline_agent_manifest | The rules of the corpus: safe language, citation policy, first calls. Call this first. | | timeline_search_reports | Search reports by text, motif, phenomenon, source type, date, stance, or evidence grade. Paginated. | | timeline_get_report | One full report with labeled claims, anchors, related reports, safety flags, and recommended phrasing. | | timeline_mandela_catalog | Mandela Effect items: remembered vs on-record variants, community and mainstream notes side by side. | | timeline_motif_map | Recurring symbols and their co-occurrence graph — the constellation, as JSON. | | timeline_story_threads | Curated arcs written three ways: belief, neutral archive, skeptical. | | timeline_events | Official science milestones and community waves on one axis, never blended. | | timeline_compare_sources | Belief / neutral / skeptical framings for one topic, plus officially-sourced shared facts. | | timeline_deepen_story | Research prompts and follow-up angles — never fabricated sources. | | timeline_stats | Corpus totals by phenomenon, motif, source type, year, grade — and what still needs sources. |

Every tool is read-only (readOnlyHint: true), local-first, and returns structured JSON with uncertainty made visible.

The site

https://timeline-pulse.vercel.app is the same corpus as a public instrument:

  • Archive — searchable reports with evidence-grade filters and a full-record drawer.
  • Timeline — official CERN anchors above the line, community waves and symbolic anchors below. One axis, never one claim.
  • Motifs — an interactive constellation of 17 recurring symbols (machine silence, rainbow bridge, serpent time, heart collider…).
  • Mandela Catalog — classic memory variants with the mainstream explanation always attached.
  • Story Threads — eight arcs, each readable through a belief / neutral / skeptic lens switch.
  • For agents — MCP install, raw JSON endpoints, llms.txt, and the language rules.

Plus one honest easter egg: press M and the site quietly Mandela-affects itself. See if you notice everything that changed.

Raw data endpoints (CORS-open)

/reports.json · /mandela-items.json · /motifs.json · /events.json · /story-threads.json · /sources.json · /llms.txt · /openapi.json

The site serves the exact JSON files the npm package ships — one corpus, three doors (site, MCP, raw JSON).

Evidence grades

| Grade | Meaning | | --- | --- | | official | Published by the institution itself — always linked | | firsthand | A person reporting their own experience | | reported | Shared accounts: forums, polls, threads | | interpretive | Community meaning-making on top of events | | symbolic | Allegory and teaching language, filed as such | | speculative | Unverified conjecture, clearly flagged |

Development

npm install
npm test        # policy guard + build + corpus validation + site-sync check + MCP smoke test
npm run build   # compile the server to dist/
npm run sync-site  # copy data/ JSON into site/ after editing the corpus
npx serve site  # run the site locally

The repo enforces its own content policy in CI: official claims must carry official URLs, speculative claims must carry safety flags, and one symbolic source family is never named — checked by hash, so the name appears nowhere, including in the check itself (scripts/check-policy.mjs).

Contributing

Reports, corrections, and motifs are welcome — see CONTRIBUTING.md and the issue templates. The fastest way to help: find official sources for anything flagged ⚑ needs source.

Documentation map

License

Code is MIT. Data: original summaries and metadata authored by the project; official facts link to their institutional sources; excerpts stay short and attributed. Details in docs/SOURCE_POLICY.md.


EST. 2026 · SEED CORPUS v0.1 · NO PHYSICS WERE HARMED ◉