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

@cocoframe/cli

v0.1.0

Published

Development, build, inspection, generation, and production tooling for CocoFrame.

Vulnerabilities

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

Links

Git

Maintainers

wiryosaputrawiryosaputra

Keywords

cocoframetypescriptserver-firstweb-framework

Readme

@cocoframe/cli

The cocoframe executable owns project discovery, inspection, read-only diagnostics, development, generation, CocoSpecs discovery, CocoUX journey and visual preview, CocoRef component approval, CocoQA evidence and release approval, local Agent Bridge MCP serving, production builds, asset serving, and startup.

Commands

  • cocoframe spec create|resume|answer|check|generate|approve manages adaptive product discovery and review artifacts under specs/<feature>/.
  • cocoframe ux create|resume|answer|check|generate|preview|feedback|approve|handoff|cancel manages journey, state, interaction, visual recommendation, PNG evidence, and CocoRef handoff under ux/<feature>/.
  • cocoframe ref create|add|audit|status|consent|decline|preview|feedback|approve|cancel manages reference audits and consent-gated component previews under refs/<name>/.
  • cocoframe qa create|resume|answer|run|record|defect|resolve|check|approve manages traceable quality evidence and release approval under qa/<feature>/; create accepts --design <profile> for Product Design Quality.
  • cocoframe inspect <project> emits routes, layouts, islands, styles, UI/icon usage, contracts, middleware, and system routes.
  • cocoframe doctor <project> [--json] [--deep] [--strict] returns actionable project, dependency, configuration, generated-artifact, security, and isolated-build diagnostics without changing the project.
  • cocoframe agent <project> serves versioned MCP discovery, lifecycle, and controlled mutation tools; agent approve|deny|cancel|expire records host-only hash-bound decisions outside the MCP tool surface.
  • cocoframe dev <project> builds and watches isolated development output.
  • cocoframe generate <project> writes typed clients, OpenAPI, and CSS module declarations.
  • cocoframe build <project> writes production server and hashed browser assets.
  • cocoframe start <project> serves the production deployment manifest.
  • cocoframe openapi <project> regenerates the OpenAPI document.

The CLI is an executable boundary rather than an application library API. Discovery/build helpers in src/project.ts are tested repository internals. Generated files are never edited manually. Verify changes with tests/project.test.ts, tests/doctor.test.ts, tests/agent.test.ts, npm run inspect, and build/E2E when browser output changes.