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

@plurnk/plurnk-meta

v1.0.5

Published

The plurnk metaproject layer, published: plugin-membership primitives (the ONE trust rule, scope-agnostic symlink-aware enumeration, deployment-root resolution), the family teaching corpus (personality, requirements, scheme docs), and the home for family

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

possumtechcompossumtechcom

Keywords

Readme

@plurnk/plurnk-meta

The plurnk metaproject layer, published — what the family shares that no single member owns.

Membership primitives (import Meta from "@plurnk/plurnk-meta"): the ONE implementation of trust, enumeration, and root resolution consumed by the daemon's plugin loader and env-defaults floor and by all four family-head scanners (schemes, mimetypes, providers, execs).

  • Meta.isTrusted(packageName, env?) — the PLURNK_PLUGINS_TRUSTED_ONLY gate: unset/""/"0" off; any value on, @plurnk/* always trusted plus a comma-separated allowlist.
  • Meta.packageDirs(nodeModulesDir) — scope-agnostic, symlink-aware enumeration of installed packages as { dir, name } candidates. Ordering and filtering are the caller's policy.
  • Meta.nearestNodeModules(fromDir) — walk up to the nearest node_modules holding the ecosystem (witness: @plurnk scope); null when absent.

The teaching corpus: PLURNK_PERSONALITY.md (the default operating policy the daemon seeds to ~/.plurnk/AGENTS.md), requirements.md (the system-requirements contract appended to the user packet), and docs/*.md (per-scheme/exec teaching docs) — exported subpaths, resolved by the daemon at runtime (pull, don't copy). See CORPUS.md.

Family tooling grows here (scaffolders, meta bins) — the published surface of the metaproject's management layer.

Third-party plugin authors: your package is discovered by ANY scope + a plurnk manifest (plurnk.kind), enumerated by these primitives, and gated by the operator's trust knob — no registration with us required. MIT.