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

@x12i/memorix-relationships

v3.1.0

Published

Memorix relationship engine: compile, discover, materialize, verify/rebuild (Phase 7 / G7). The only trusted production relationship-link writer.

Readme

@x12i/memorix-relationships

Trusted relationship engine: compile definitions, discover, materialize, verify, and rebuild four-field links.

This is the only production path that writes relationship links. Remote clients use HTTP; ad-hoc /links mutation is rejected (405).

Install

npm install @x12i/[email protected]

| Audience | Use this package? | |----------|-------------------| | Remote app | No/api/relationships | | Platform / pipelines | Yes |

Core API

import { createRelationshipEngine } from "@x12i/memorix-relationships";

const engine = createRelationshipEngine({ /* store, metadata resolver, data reader */ });

// Dry-run candidates
await engine.discoverAndMaterialize(scope, definitionId, { dryRun: true });

// Persist links
await engine.discoverAndMaterialize(scope, definitionId, { dryRun: false });

await engine.verify(scope, definitionId);
await engine.rebuild(scope, definitionId);

Lifecycle:

relationship definition (metadata)
  → discover (candidates, service-held)
  → materialize (four-field links in store)
  → verify / rebuild

Hard rules

  • Links are exactly four fields (relationshipId, relationshipDefinitionId, fromRecordId, toRecordId).
  • Never copy related payloads into the source record (associated* as storage is forbidden).
  • Neighbor content is read at expand time, not embedded.

Related

| Need | Package | |------|---------| | Persistence adapter | @x12i/memorix-relationship-store | | Compose / expand reads | @x12i/memorix-data | | Pipeline steps | relationship-discover / relationship-write in @x12i/memorix-pipeline |

Docs

npm test