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

concept-miner

v1.1.0

Published

Deterministic concept extraction from natural language.

Readme

concept-miner

Deterministic concept extraction from natural language.

Purpose

concept-miner is productized as a CommonJS Node.js package for deterministic, contract-driven concept extraction.

Given text input, it extracts explicit concepts in canonical, deduplicated, traceable form.

Current State

This repository currently contains:

  • product-facing contracts:
    • openapi/openapi.yaml
    • schema/concepts.schema.json

The full productization backlog is tracked in TODO.md, and staged milestones are in ROADMAP.md.

Runtime boundary:

  • package payload is product runtime only.

Target Mode Model

  • default extended mode (default and only product mode): extraction with wikipedia/wikipedia-title-index information.

Development

npm ci
npm run lint
npm test
npm run dev:check
npm run dev:report:metrics
npm run dev:report:maturity
npm run ci:check
$env:RELEASE_TARGET_VERSION = (node -p "require('./package.json').version")
npm run release:check

JavaScript API (Current)

const { extractConcepts, validateConcepts } = require("concept-miner");

const doc = await extractConcepts("alpha beta alpha", {
  mode: "default-extended",
});

const validation = validateConcepts(doc);

CLI (Current)

concept-miner extract --text "alpha beta alpha" --mode default-extended --out concepts.json
concept-miner validate-concepts --in concepts.json

Optional runtime enrichment flags for extract:

concept-miner extract --text "alpha beta alpha" \
  --mode default-extended \
  --wikipedia-title-index-endpoint "http://127.0.0.1:32123" \
  --wikipedia-title-index-timeout-ms 1500

In default-extended mode, wikipedia-title-index is required. If unavailable or timed out, extraction hard-fails.

REST API

The REST contract is specified in openapi/openapi.yaml, and an in-repo runtime server is available:

npm run serve:api

Default server bind:

  • http://127.0.0.1:32180

POST /v1/concepts/extract:

curl -sS -X POST "http://127.0.0.1:32180/v1/concepts/extract?view=compact" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "A webshop accepts orders."
  }'

Default-extended runtime enrichment options:

{
  "text": "The quick brown fox jumps over the lazy dog.",
  "options": {
    "mode": "default-extended",
    "wikipedia_title_index_endpoint": "http://127.0.0.1:32123",
    "wikipedia_title_index_timeout_ms": 1500
  }
}

Release

This repository follows a dual-stream release model:

  • Git stream:
    • versioned commits
    • annotated tags
    • optional GitHub Releases
  • npm stream:
    • npm publish
    • registry propagation checks
    • post-publish smoke tests

Relevant documentation:

  • docs/NPM_RELEASE.md
  • docs/REPO_WORKFLOWS.md
  • docs/OPERATIONAL.md
  • docs/DEV_TOOLING.md
  • docs/RELEASE_NOTES_TEMPLATE.md
  • docs/releases/v0.10.0.md
  • docs/releases/v1.0.0.md
  • docs/releases/v1.0.1.md
  • docs/releases/v1.0.2.md
  • docs/releases/v1.0.3.md
  • docs/releases/v1.0.4.md
  • docs/releases/v1.0.5.md
  • docs/BASELINE_TEST_RUN.md
  • docs/FROZEN_REFERENCES_POLICY.md
  • docs/GENERATED_REPORT_ARTIFACTS_POLICY.md
  • docs/CONTRACT_ALIGNMENT.md
  • docs/GUARANTEES.md
  • docs/STATUSQUO.md
  • docs/TEMPLATE_SETUP.md
  • CONTRIBUTING.md
  • SECURITY.md
  • CHANGELOG.md
  • project.config.json

Release automation:

  • .github/workflows/release.yml provides a manual workflow_dispatch release check.

License

See LICENSE.