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

@disclosureos/origins

v1.0.0

Published

Classification taxonomy for the DisclosureOS ecosystem — origin hypotheses, OCS taxonomy, and reference systems

Readme

@disclosureos/origins

License: MIT

Classification taxonomy for the DisclosureOS ecosystem — the Origins layer. It answers "what might explain the observation?" via the Origin Classification System (OCS): a tree of origin hypotheses across the Physical, Psychosocial, and Metaphysical domains, plus typed mappings to the reference systems researchers already use (Hynek, Vallée, AARO, GEIPAN).

The DisclosureOS model

DisclosureOS is a five-part standard. Each part answers one question about an observation; @disclosureos/schema binds the package-owned pieces into one portable contract (a single TS type + JSON Schema + non-stripping parse).

| Part | Package surface | Question it answers | |---|---|---| | Records | @disclosureos/records | What was observed? | | Observables | @disclosureos/observables | What anomalous characteristics did it show? | | Origins | @disclosureos/origins | What might explain it? | | Claims | @disclosureos/records/shared | Who assessed it, why, and on what evidence? | | Scoring | @disclosureos/scoring | How complete / compelling is the case? |

Supporting packages: @disclosureos/schema (the portable contract that composes the package-owned pieces), @disclosureos/cli (tooling), and @disclosureos/examples (the runnable golden path). (You are here: Origins.)

Built on records

This package depends on @disclosureos/records, the shared substrate — it reuses its confidence and claim primitives. Importing this package augments the Observation type with the origin slot:

import '@disclosureos/origins'; // `observation.origin` is now typed

See it end to end. examples/golden-path.ts takes one observation through every layer — records → observables → origins → scoring, validated as a whole by @disclosureos/schema — in a single type-checked file. Run it with pnpm --filter @disclosureos/examples golden-path.

Migrating an existing dataset? See examples/migration-path.ts and the onboarding workspace.

Install

pnpm add @disclosureos/origins @disclosureos/records zod

Quick start

import { createOriginClaim, getNode } from '@disclosureos/origins';
import type { Observation } from '@disclosureos/records';

const observation: Observation = {
  // ...records core fields...
  origin: [
    { primaryHypothesis: '1.1.3', confidence: 0.9, evaluatedBy: 'analyst-a' },
  ],
};

getNode('1.1.3'); // resolve an OCS node by id

The origin slot is an array of competing claims (one per evaluator/verdict), so contested classifications are represented directly. Every primaryHypothesis / alternativeHypotheses node id is validated against the live taxonomy.

⚠️ A raw ObservationSchema.parse() strips this slot. Validate enriched records with validateOriginClassification() (this package) or parseEnrichedObservation() from @disclosureos/schema.

Subpath exports

| Subpath | Contents | |---|---| | @disclosureos/origins | OriginClaim, createOriginClaim, getNode, validateOriginClassification | | @disclosureos/origins/taxonomy (+ /physical, /psychosocial, /metaphysical) | The OCS tree + traversal | | @disclosureos/origins/reference/* | Hynek · Vallée · AARO · GEIPAN reference systems | | @disclosureos/origins/{classification,labels,constants,guards,factories,formatters} | Claims + the DX quintet | | @disclosureos/origins/schema | The committed JSON Schema (origins.schema.json) |

Standard Schema

The Zod schemas here implement Standard Schema v1 via their ~standard property — a guarantee of Zod 4. Any Standard-Schema-compatible validator or framework can consume them directly, with no DisclosureOS-specific adapter.

License

MIT © Disclosure Foundation