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

@captiveorigins/onetaxonomy-core

v0.1.0-alpha.2

Published

OneTaxonomy core: taxon concepts, classifications and phylogenetic hypotheses, with validation, bounded traversal, MRCA, tri-state monophyly, curated selections, coverage reports and snapshot diffs. No React, CMS, database or platform dependency.

Readme

@captiveorigins/onetaxonomy-core

The scientific core of OneTaxonomy: taxon concepts, names, classifications and phylogenetic hypotheses, with validation, bounded traversal, MRCA and tri-state monophyly. No dependencies; no DOM, Node, React, CMS or database. It runs in browsers, Node, workers and desktop webviews.

import { assessTaxon, findMRCA, indexDataset, isMonophyletic, sealSnapshot, validateDataset } from '@captiveorigins/onetaxonomy-core'

const problems = validateDataset(snapshot)          // diagnostics; nothing is repaired silently
const sealed = sealSnapshot(snapshot)               // checksummed and frozen
const data = indexDataset(sealed)

const tree = data.phylogeny('archelosauria')        // a rooted hypothesis
findMRCA(tree, ['t-testudines', 't-aves'])          // { status: 'found', node: 'archelosauria', hypothesis }
isMonophyletic(tree, ['t-crocodylia', 't-aves'])    // { status: 'monophyletic', reason: 'complete-clade', … }

// A classification taxon against a hypothesis, through explicit concept mappings only:
assessTaxon(data.classification('traditional'), 'c:reptilia', tree)
// { status: 'not-monophyletic', missing: ['t-aves'], … }
assessTaxon(data.classification('traditional'), 'c:reptilia', null)
// { status: 'indeterminate', reason: 'classification-only' }
  • Results are relative to one hypothesis ({ id, version }) and carry caveats (partial-sampling, unmapped-members, …).
  • Unrooted trees give no MRCA or clade claims; forests get no invented common ancestor; polytomies are unresolved (indeterminate) unless you pass { polytomies: 'hard' }.
  • Traversal (getChildren, getAncestors, getLineage, getDescendants) is iterative and accepts maxDepth / limit, returning truncated when cut.

Curation, coverage and releases

import { applySelection, diffSnapshots, extractSubset, getCoverageReport, referenceImpact } from '@captiveorigins/onetaxonomy-core'

const result = applySelection(data, selection)            // curated + ancestor paths, omitted branches, diagnostics
const coverage = getCoverageReport(data, {
  classification: selection.classification, included: result, phylogeny: 'my-tree',
  knownToScience: { [turtles]: { count: describedSpecies, rank: 'species', source: 'the checklist you cite' } },
})                                                        // dataset · hypothesis · known to science (only as you state it)
const subset = extractSubset(snapshot, { id, version, createdAt, classification: selection.classification, include: result })
const changes = referenceImpact(diffSnapshots(oldRelease, newRelease), mySavedIds) // renamed, relocated, split/merge candidates…

schema/snapshot.schema.json (exported as @captiveorigins/onetaxonomy-core/schema/snapshot.schema.json) describes the snapshot format for non-TypeScript tools.

See the data schema and invariants.