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-opx-pack

v3.0.7

Published

Permanent opx/fieldstone acceptance pack: agent metadata, fixtures, opx-source, harness.

Readme

@x12i/memorix-opx-pack

Permanent opx acceptance pack for Memorix: agent metadata, fixtures, a localhost opx-source, harness, and APS simulation assets.

This is tier-4 product vocabulary (object types, pipelines, views) on top of the platform — not an engine.

Platform gate acceptance uses fresh sandbox* (or similar) orgs with agentIds: ["opx"]. Never point acceptance at live customer orgs.

Install

npm install @x12i/[email protected]

Usually you run it from the monorepo rather than depending on it from a product app.

Contents

| Path | Purpose | |------|---------| | metadata/ | Agent opx, child agents, abstracts, object types, relationships, views, pipelines, sources, services | | fixtures/opx-source-data.json | Deterministic source payloads (legacy path; mirrored under simulation/data/) | | simulation/ | APS package-sim assetspack.simulation.json + data (MX-CF-FR-022). Host rebuild blocked on APS-CF-CR-005 | | opx-source/server.mjs | Temporary local REST until APS package-sim replaces it — do not grow as a second simulator | | scripts/harness.mjs | up / down / reset / accept | | examples/v2/ | Golden memorix-record/2 records |

Exports: . · ./metadata/* · ./fixtures/* · ./simulation/*.

Simulation (Studio)

  • Engine: @x12i/api-simulator only — see docs/connector-framework/APS-CF-requirements.md (FR-009…012) and MX-CF-simulation-requirements.md.
  • Connectors: opx-rest / rest advertise capabilities.simulation: true.
  • External packs: ship simulation/pack.simulation.json the same way; do not invent a private mock HTTP server. If APS lacks an API, write an FR/CR.

KnowX (knowledge extract / associate) lives in @x12i/memorix-knowx-pack (agent knowx, child of opx).

Quick start

Prefer the monorepo stack (opx-source :5102, service :5100, Studio :5101, stack-status :5103):

# from repo root
node scripts/dev-stack.mjs
# opens /_live for service + opx-source

# with Nexum worker (zone nexum · worker :7500 · read :7502 · compiler :7504)
node scripts/dev-stack.mjs --nexum

opx-source complies via @x12i/core-service (zone port, /health, /_live).

Services (pack): opx-enrich-priority (enrich), nexum (analyze · MEMORIX_NEXUM_URL default :7500). Nexum is the knowledge-graph analyze worker (successor to Graphifier; Graphifier is not supported). Sample pipelines: opx-nexum-analyze (Nexum + write-record mode nexum).

Pack-only:

npm install && npm test
node scripts/harness.mjs up          # OPX_SOURCE_PORT default 5102
node scripts/harness.mjs accept      # run acceptance against isolated org
node scripts/harness.mjs down

How it connects

opx-source (:5102)
  → Memory pull (credentialRef / fixture connector)
  → pipelines in metadata/
  → data + relationships
  → Studio Explore / Operate

Views in this pack are also the descriptor source for data-journey coverage expected slots when metadata is installed.

Docs