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

@closurenetwork/ide

v0.2.4

Published

Closure Agent Pack installer — npx @closurenetwork/ide init. Rails from Platform Knowledge; local files are never product SoT.

Downloads

66

Readme

@closurenetwork/ide

Closure Agent Pack for your IDE. Published on npmjs.org under the closurenetwork org — never clone this repo.

This package is a thin installer. AGENTS.md, Cursor rules, and Closure-way skills are fetched from Closure Platform Knowledge (GET /api/public/ide/pack) — not hardcoded here.

The authoring contract

Your IDE agent doesn't just get tools — it gets a runtime that holds up its half of the loop:

  1. The runtime teaches. platform_docs_search grounds paradigm answers in the docs, the book The Last Application, and the whitepaper. platform_taxonomy serves the live vocabulary — every schema, component kind, workflow node type, and composition rule, straight from the registries that will execute them.
  2. The runtime checks before you write. platform_validate dry-runs any DataObject, Experience graph, or workflow graph and returns the exact violations.
  3. The runtime gates what ships. Creativity is welcome; the ship bar is not negotiable. platform_experience_verify runs the same server-side craft gates a governed build enforces (design system, taxonomy-pure components, i18n, discoverability, accessibility). Gate keys are server-owned — clients can't mark their own work as passing.
  4. The runtime delegates. Governed builds (platform_build_start) hand creative planning nodes to your agent's context on waiting_ide — original IA, copy, and brand voice, inside the gates.
  5. The runtime ships. Dev is the live graph; Test and Prod serve pinned versions. platform_experiences_health shows pin state, platform_experiences_promote snapshots Dev and pins Test/Prod, and platform_release_snapshot / platform_release_promote cut org-wide releases — with the same role, policy, and quality-gate checks the console enforces.
  6. The runtime learns. Anonymous friction telemetry (failed calls, unanswered docs searches, gate failures — never prompts, code, or identity) auto-opens platform Issues with recommended fixes. Opt out with CLOSURE_TELEMETRY=0.

Full docs: closureapps.com/docs/ide.

Install

Run this in a normal terminal (Cursor’s integrated terminal or iTerm/Terminal.app) — not via the Agent’s Shell tool:

npx @closurenetwork/ide@latest init

Then reload MCP → Connect → call platform_status → platform_knowledge_skills_pull.

Why not from the Agent?

Cursor sandboxes agent shell commands. init needs outbound network (registry.npmjs.org + Closure) and writes .cursor/mcp.json. Cursor hard-protects .cursor/*.json from the agent (by design — so agents can’t silently rewrite MCP/auth config). A real terminal has neither restriction. After init, the agent can still refresh rails via npx @closurenetwork/ide sync (rules/skills live under writable .cursor/ subdirs) and work through Connect.

On-prem / local Studio

STUDIO_URL=http://localhost:3021 npx @closurenetwork/ide init
# or
CLOSURE_IDE_PACK_URL=http://localhost:3021/api/public/ide/pack npx @closurenetwork/ide init

Commands

| Command | Purpose | |---------|---------| | init | Fetch pack, write rails, register MCP | | sync | Re-fetch pack (Knowledge updates) | | status | Local + remote pack health | | doctor / update | Aliases of status / sync |

Auth — prefer Connect

{
  "mcpServers": {
    "closure": {
      "url": "https://mcp.closureapps.com",
      "type": "http"
    }
  }
}

Fallback — stdio + API key

The stdio shim exposes the core authoring subset (status, scaffold, craft, collect, build, workflows, agent task/submit). The full authoring contract above — grounding, taxonomy, validation, verification, promotion, feedback — is served by the hosted HTTP MCP; prefer Connect.

npx @closurenetwork/ide init --stdio
{
  "mcpServers": {
    "closure": {
      "command": "npx",
      "args": ["-y", "@closurenetwork/ide", "mcp-stdio"],
      "env": {
        "STUDIO_URL": "https://closureapps.com/console",
        "STUDIO_API_KEY": "csk_…"
      }
    }
  }
}

What gets written

| Path | Role | |------|------| | .closure/pack.json | Pack version for sync | | AGENTS.md / CLAUDE.md | Always-on Closure constitution | | .cursor/rules/ · .cursor/skills/ | Cursor rails | | .claude/skills/ | Claude Code rails | | .github/copilot-instructions.md | Short Copilot extract | | .cursor/mcp.json | Platform MCP registration |

Product Experiences stay on the graph. Local files are adapters only.

Related

| Repo | Role | |------|------| | platform | Studio, Knowledge, MCP, /api/public/ide/pack | | deploy | Self-host |

License

Apache-2.0