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

create-academic-research

v0.3.0

Published

Scaffold a four-entity academic research project: SOTA, survey, contributions, papers — one root bibliography, MCP-verified citations, agent skills.

Readme

Create Academic Research

npm Validate License: MIT

Scaffold a four-entity academic research project with one command: SOTA → survey → contributions → papers, one root bibliography, MCP-verified citations, agent skills included.

npm create academic-research@latest my-project

What it creates

my-project/
├── README.md  AGENTS.md  CLAUDE.md
├── references.bib       # THE single bibliography (1:1:1 with the SOTA)
├── .mcp.json            # arxiv + semantic-scholar + dblp always on
├── pyproject.toml       # uv workspace: one venv for all contributions
├── Makefile             # make check | pdfs | survey | contribution | paper
├── scripts/check.py     # structure validator
├── sota/                # papers/<citekey>/{paper.pdf,synthesis.md,metadata.yaml} + index + queue
├── survey/              # survey.tex + committed survey.pdf + coverage.md
├── contributions/       # self-contained badge-compliant units (_template/)
└── papers/              # one folder per venue submission (_template/)

The wizard asks for a title, a one-line topic, optional MCP servers (openalex pre-checked; zotero and overleaf opt-in), and installs the companion academic-research-skills project-locally. Flags: --yes, --no-install-skills, --no-git.

The model

  • SOTA: digesting a paper atomically produces its folder (PDF + standard synthesis + metadata with citation graph), its bib entry, and its index row. A citation exists only if a scholarly MCP lookup produced it — provenance is recorded per paper and enforced by make check.
  • Survey: one single-column LaTeX document that digests every synthesis, groups the SOTA, and ends with gaps & research directions. coverage.md makes updates diff-driven when the SOTA changes.
  • Contributions: each one self-contained and badge-general compliant, with a report detailed enough to write papers from.
  • Papers: per-venue folders with framing, manuscript on the venue template, packaged artifacts, correspondence, and immutable submission archives.

Generated projects need: git, make, python3 (≥3.11), latexmk, and uv (uvx runs the MCP servers). No Node at runtime (except the optional openalex server).

Develop this package

npm install
npm run typecheck
npm test
npm pack --dry-run

The test suite needs python3 ≥ 3.11 on PATH (one test validates generated TOML with tomllib); CI uses 3.12.

Release

Tag-driven. Bump package.json, commit, tag vX.Y.Z, push the tag; the release workflow validates, publishes to npm, and creates a GitHub release.