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

@soloworks/smking-wizard

v0.10.0

Published

Page Zero OAuth connection, shared public guides and installed SDK diagnostics. No embedded AI or automatic installation.

Readme

Page Zero CLI

0.10.0 replaces the legacy embedded AI wizard. Node 20.10+ is required. Only OAuth connection, public guides and installed SDK diagnostics remain. No Ink/React UI, model calls, package installation, automatic repair, host scheduling or deployment.

pnpm dlx @soloworks/smking-wizard@latest --help
pnpm dlx @soloworks/smking-wizard@latest connect --site-url=https://your-site.example
pnpm dlx @soloworks/smking-wizard@latest instructions --framework=laravel
pnpm dlx @soloworks/smking-wizard@latest doctor --json --surfaces=aeo,cms
pnpm dlx @soloworks/smking-wizard@latest connect --dry-run

The default command is connect. Browser OAuth selects a workspace and site; an interactive terminal is required to confirm local settings. Production-like environments and dirty Git trees are refused unless explicitly overridden with --allow-prod / --allow-dirty. These overrides do not skip confirmation. Use the actual website HTTPS origin, never a Git remote URL. SMKING_SAAS_URL selects the backend; default: https://getpagezero.com. Only HTTPS origins are accepted, except loopback HTTP for local development. Set SMKING_WIZARD_CLIENT_ID only when the backend explicitly uses another public client.

connect only writes SMKING_API_KEY, SMKING_BASE_URL, SMKING_WEBHOOK_SECRET and, when configured by the same source, SMKING_DELIVERY_NOTIFICATIONS_SCOPE. Laravel uses .env; Next.js uses .env.local. Differing values require confirmation. Unrelated settings and existing file permissions are preserved. New files are 0600; symlinks, duplicate managed settings and files owned by another user are refused. In a Git repository the environment file must also be ignored and untracked; the CLI refuses unsafe files without editing .gitignore or removing tracked data. Tokens stay in memory. Delivery mode, CMS path, resources, scheduling and installation are handled by your own coding assistant according to the shared public guide.

instructions fetches /docs/sdk/laravel.md or /docs/sdk/nextjs.md from the selected backend without authentication. It never executes Markdown or includes private settings. These publicly served files are the single installation source shared by Dashboard and CLI; the private GitHub repository is not a customer documentation endpoint.

doctor invokes the installed artisan command or the installed Next.js SDK binary. It never uses dlx or downloads a missing SDK. It can perform the SDK's normal diagnostic network checks. JSON output is redacted; doctor passing is not delivery activation. --dry-run on any command performs only local inspection, without OAuth, network or writes. --help and --version work offline and do not load the OAuth browser opener.

Existing SDKs, WordPress OAuth and historical report data are unchanged. Legacy wizard gateway, install-prompt and AI failure-report submission are removed; old CLI versions must upgrade. Install the new SaaS endpoints and public guides before publishing CLI 0.10.0, and coordinate Dashboard deployment with the registry release.

The public guides distinguish Laravel durable copies/background work from Next.js native cache/webhook/CDN. No customer database is required.