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

@murmurations-ai/signals

v0.8.0

Published

Default SignalAggregator for the Murmuration Harness — github + filesystem sources with interim trust taxonomy.

Downloads

1,548

Readme

@murmurations-ai/signals

Default SignalAggregator for the Murmuration Harness. Composes three real sources — github-issue (via @murmurations-ai/github), private-note (filesystem), inbox-message (filesystem) — into a single ordered SignalBundle per wake.

Owned by Architecture Agent #23 with an interim trust taxonomy pending Security Agent #25's harness#4 ratification.

See docs/adr/0013-signal-aggregator.md for the full design.

Why a separate package?

The SignalAggregator interface lives in @murmurations-ai/core so the daemon can reference it without depending on any concrete source package. The default implementation depends on @murmurations-ai/github, and @murmurations-ai/github depends on @murmurations-ai/core. Putting the default implementation in its own package breaks the cycle without weakening the architectural separation.

Scope (1B-d)

  • Implemented: github-issue, private-note, inbox-message
  • Deferred: pipeline-item, governance-round, stall-alert — these depend on Phase 2+ infrastructure (pipeline artifacts, governance plugin runtime, stall detector).

Trust taxonomy (interim)

| Source | Default trust | | --------------------------------------- | -------------- | | github-issue from trusted scope | trusted | | github-issue from public repo | semi-trusted | | private-note at agents/<id>/notes/ | trusted | | inbox-message (default) | semi-trusted | | inbox-message from allowlisted sender | trusted |

See packages/core/src/signals/index.ts for the content-trust separation convention (body fields are always one step below metadata trust).