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

@context-action/sem-foundation-repository

v0.1.1

Published

Bounded Git history, revision, worktree, and project-snapshot primitives for SEM tools

Readme

@context-action/sem-foundation-repository

Shared repository runtime primitives for SEM-backed tools.

This package owns the mechanics that must be identical when a tool analyzes current state or a historical commit:

  • bounded Git revision and first-parent range reads;
  • detached worktree creation, checkout, and cleanup;
  • symbolic Git ref resolution before detached worktree materialization;
  • canonical repository/project containment checks;
  • generic analysisProjects traversal through a callback.

It intentionally does not own SEM execution, architecture registries, document indexes, policy evaluation, or report schemas. Consumers provide the project analyzer and keep their own evidence and missing-project policy.

@context-action/sem-foundation-contracts supplies the shared AnalysisProject, GitCommitRecord, and RepositoryRevision data contracts.

analyzeHistoricalProjects materializes each requested project in the target commit worktree and lets the consumer choose the missing-project policy. The architecture-governance consumer skips a project that does not exist at that revision and records missing-at-revision in the symbol snapshot; the repository runtime itself remains policy-neutral.

GitHistoryReader.listRange({ maxCommits }) uses 512 commits as its default but accepts a larger explicit limit. analyzeHistoricalProjects accepts the Foundation contract limit options so callers can raise the shared analysis-project and extension bounds without duplicating validation logic.