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

@plures/pares-modulus

v0.2.0

Published

Plugin registry for pares-radix — curated, gated collection of plugins

Readme

pares-modulus

The plugin registry for pares-radix — a curated, gated collection of plugins that radix discovers, browses, and installs from directly.

Modulus works like nixpkgs: a single repo containing plugin definitions, metadata, and source. Anyone can submit a plugin via PR. Submissions go through automated gates (CI, type-check, security scan, size audit) and maintainer review before merging.

How It Works

pares-radix (app)
    │
    ├── radix plugin browse     →  fetches registry/index.json from modulus
    ├── radix plugin install X  →  pulls plugin source from modulus/plugins/X/
    └── radix plugin update     →  checks for newer versions in registry

For Users (in radix)

# Browse available plugins
radix plugin browse

# Install a plugin
radix plugin install financial-advisor

# Update all plugins
radix plugin update

For Plugin Authors (submitting to modulus)

# 1. Fork pares-modulus
# 2. Add your plugin
mkdir plugins/my-plugin
# 3. Create the required files (see structure below)
# 4. Open a PR — automated gates run

Repository Structure

pares-modulus/
├── registry/
│   ├── index.json              # Machine-readable plugin catalog
│   └── schema.json             # Plugin manifest validation schema
├── plugins/
│   ├── financial-advisor/
│   │   ├── manifest.json       # Plugin metadata (name, version, deps, etc.)
│   │   ├── src/                # Plugin source code
│   │   │   ├── index.ts        # RadixPlugin export
│   │   │   ├── pages/          # Svelte components
│   │   │   ├── rules/          # Praxis inference rules
│   │   │   └── stores/         # Domain state
│   │   ├── tests/              # Plugin tests
│   │   └── README.md           # Plugin documentation
│   ├── vault/
│   ├── sprint-log/
│   ├── netops-toolkit/
│   └── agent-console/
├── gates/                      # Submission gate scripts
│   ├── validate-manifest.ts    # Schema validation
│   ├── security-scan.ts        # Dependency audit + no secrets
│   ├── size-audit.ts           # Bundle size limits
│   └── type-check.ts           # TypeScript strict compliance
├── scripts/
│   ├── build-registry.ts       # Rebuilds registry/index.json from plugins/
│   └── validate-all.ts         # Runs all gates on all plugins
└── .github/
    └── workflows/
        ├── plugin-gate.yml     # PR gate: runs all checks on changed plugins
        ├── build-registry.yml  # Post-merge: rebuilds index.json
        └── ...                 # Standard plures automation

Plugin Manifest (manifest.json)

Every plugin must include a manifest.json:

{
  "id": "financial-advisor",
  "name": "Financial Advisor",
  "version": "0.1.0",
  "description": "AI-powered personal finance management with praxis inference",
  "author": "plures",
  "license": "MIT",
  "icon": "💰",
  "keywords": ["finance", "budgets", "transactions", "categorization"],
  "homepage": "https://github.com/plures/pares-modulus/tree/main/plugins/financial-advisor",
  "repository": "https://github.com/plures/pares-modulus",
  "radix": ">=0.1.0",
  "dependencies": [],
  "peerDependencies": {
    "@plures/design-dojo": ">=0.1.0"
  },
  "entry": "src/index.ts",
  "size": {
    "source": "25KB",
    "estimated_bundle": "40KB"
  }
}

Submission Gates

All PRs that touch plugins/ must pass:

| Gate | Description | Failure = | |---|---|---| | Manifest Validation | manifest.json matches schema, all required fields present | Block | | Type Check | tsc --noEmit --strict on plugin source | Block | | Security Scan | No hardcoded secrets, dependency audit clean | Block | | Size Audit | Source under 500KB, no binary blobs | Block | | Tests | Plugin tests pass (if tests/ exists) | Warn | | Radix Compatibility | Plugin exports valid RadixPlugin interface | Block | | Maintainer Review | Human approval required | Block |

Registry Index

registry/index.json is auto-generated on merge and serves as the catalog radix queries:

{
  "version": 1,
  "generated": "2026-03-27T18:00:00Z",
  "plugins": [
    {
      "id": "financial-advisor",
      "name": "Financial Advisor",
      "version": "0.1.0",
      "description": "AI-powered personal finance management with praxis inference",
      "author": "plures",
      "icon": "💰",
      "keywords": ["finance", "budgets"],
      "radix": ">=0.1.0",
      "size": "25KB",
      "path": "plugins/financial-advisor"
    }
  ]
}

Community Guidelines

  • One plugin per directory in plugins/
  • Plugin IDs are unique and kebab-case
  • Breaking changes require a version bump in manifest.json
  • Plugins must be self-contained — no imports between plugins
  • Tests are encouraged — plugins with tests get a "tested" badge in the registry
  • Inactive plugins (no updates for 12 months) get a deprecation warning

License

MIT — individual plugins may have their own licenses specified in their manifest.json.