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-base-format

v1.2.1

Published

Memorix base record format: fixed skeleton (recordId, concept with _extIdentifier, data, _*), open buckets, ContentTypeMeta, validator, CLI.

Readme

@x12i/memorix-base-format

Source of truth for the fixed Memorix record envelope (present tense).

Product open-bucket names (associated*, analytics, enrichment, insights, …), object-type recipes, and Catalox descriptors are not defined here. Those live in @x12i/memorix-format and entity descriptors.

Envelope meta: meta/envelope.json (loaded via loadBaseEnvelopeMeta). Present-tense only — legacy roots belong in compat / memorix-format migrate, not envelope law.

Normative requirements: docs/memorix-base-format-requirements.md.

What base owns

| Category | Keys | |---|---| | Identity | recordId, concept | | Core | data | | Underscore | any _… root (machine-only; e.g. _system.state) | | Open | everything else (names not reserved) |

Identity vs content

  • recordId — join plumbing across content types for the same subject. Not human/LLM content.
  • concept.title — human-readable display name.
  • concept._extIdentifier — machine identity object: kind, same-named value, and deterministic key (kind + kind-value + other scalar fields in sorted order, :-joined). How kind / title are chosen for an object type is defined on the entity descriptor, not in this package.
  • _system.state — when present: active | archived | superseded. Writers SHOULD set active on new records.

What base does not own

  • Product / Catalox object type names (items, groups, …)
  • Known open-bucket vocabularies (analytics, associated*, …)
  • Key+title recipes per object type

Install

npm install @x12i/memorix-base-format

Abstract example

{
  "recordId": "rec-item-1",
  "concept": {
    "_extIdentifier": {
      "kind": "sku",
      "sku": "SKU-100",
      "key": "sku:SKU-100"
    },
    "title": "Blue widget"
  },
  "data": { "sku": "SKU-100", "color": "blue" },
  "_system": { "state": "active" }
}

SDK

import {
  validateMemorixBaseRecord,
  classifyRootKey,
  parseContentTypeMeta,
} from "@x12i/memorix-base-format";

const result = validateMemorixBaseRecord(record);
classifyRootKey("analytics"); // "open" — no special case

const meta = parseContentTypeMeta({
  objectType: "items",
  contentType: "snapshots",
  openBuckets: {
    analytics: { kind: "rollup", shape: "object" },
  },
});
validateMemorixBaseRecord(record, { meta: meta.meta });

CLI

npx memorix-base-format validate ./record.json
npx memorix-base-format validate ./records/ --meta=./meta.json --json
npx memorix-base-format inspect ./record.json
npx memorix-base-format docs memorix-base-format-requirements.md

Related