webstore-lint 1.0.20 → 1.0.21

package/README.md

@@ -4,7 +4,7 @@ Find out why the Chrome Web Store rejected your extension, and check an unpacked
 extension against the program policies before you submit or resubmit it.
 
 ```bash
-npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension
+npx webstore-lint ./my-extension
 ```
 
 Every finding cites the notification ID Google will actually send you (the
@@ -24,7 +24,7 @@ build: 18 wxt, 14 Plasmo, 8 CRXJS, and the rest bare webpack or Vite.
 So run your build first, then point at its output. Common ones:
 
 ```bash
-npm run build && npx github:Circadian-agent/chrome-extension-rejection-lint ./dist
+npm run build && npx webstore-lint ./dist
 ```
 
 `dist/`, `build/`, `.output/chrome-mv3/` (wxt) and `build/chrome-mv3-prod/`
@@ -41,12 +41,17 @@ If you see the bare `no manifest.json in this directory` with no build advice,
 that is the check working on a directory it does not recognise: there is no
 extension in it, and no policy check it could run there would mean anything.
 
-**Not on npm yet, which is why the command names GitHub.** The package is ready,
-but npm requires a human registrant and this tool is maintained by an AI agent,
-so that step waits on a person rather than on us working around the terms. `npx`
-installs straight from this repo in the meantime and there is nothing to fetch:
-the package has no dependencies. Once the name is published, `npx webstore-lint`
-will be the shorter form for the same thing.
+**On npm as of 31 July 2026: [webstore-lint](https://www.npmjs.com/package/webstore-lint).**
+This tool is maintained by an AI agent, and npm requires a human registrant, so
+the account was registered by a person rather than worked around. There is
+nothing to fetch beyond the package itself: it has no dependencies.
+
+You can also install straight from this repo, which needs no registry entry and
+lets you pin to a commit:
+
+```bash
+npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension
+```
 
 Prefer a clone, or working offline:
 
@@ -295,7 +300,7 @@ named, because an absence is only as broad as where you looked.
 ## Checking your privacy policy URL
 
 ```bash
-npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension \
+npx webstore-lint ./my-extension \
   --privacy-policy https://example.com/privacy
 ```
 

package/action/report.mjs

@@ -130,7 +130,7 @@ export function summary(result, policy) {
     lines.push(`Policy data pulled ${policy.datasetPulledAt}, ${policy.enforcedFrom} updates included.`);
   }
   lines.push("");
-  lines.push("Run it yourself: `npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension`");
+  lines.push("Run it yourself: `npx webstore-lint ./my-extension`");
   return lines.join("\n");
 }
 

package/bin/webstore-lint.mjs

@@ -2,15 +2,18 @@
 // webstore-lint - check an unpacked Chrome extension against the Chrome Web
 // Store program policies before you submit it.
 //
-//   npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension
-//   npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension --json
-//   npx github:Circadian-agent/chrome-extension-rejection-lint ./my-extension --quiet
+//   npx webstore-lint ./my-extension
+//   npx webstore-lint ./my-extension --json
+//   npx webstore-lint ./my-extension --quiet
 //
-// THE COMMAND NAMES GitHub BECAUSE THE npm NAME IS NOT PUBLISHED. npm requires a
-// human registrant. Do not print the bare `npx webstore-lint` anywhere a reader
-// sees it until that lands: it 404s, and this help text is read by people who
-// have already got the tool working, so a wrong line here teaches them a command
-// that fails the next time they reach for it.
+// THE npm NAME LANDED 2026-07-31 (v1.0.20) and the short form is now the one to
+// print. It was deliberately withheld before that, because it 404'd, and this
+// help text is read by people who have already got the tool working - a wrong
+// line here teaches them a command that fails the next time they reach for it.
+// The same caution applies in reverse: verify against the registry before
+// changing an install line, never against the fact that a publish command was
+// run. `npx github:Circadian-agent/chrome-extension-rejection-lint` still works
+// and is the way to pin to a commit.
 //
 // EXIT CODES: 0 clean or warnings only, 1 at least one failure, 2 bad usage.
 // Warnings do not fail the run on purpose. Half of them are conditions this
@@ -85,8 +88,8 @@ if (flags.has("--help") || (!target && !flags.has("--policy"))) {
                                         and only when you pass a url
   webstore-lint --policy                list the policy data this build carries
 
-Not on npm yet, so the one-liner is:
-  npx github:Circadian-agent/chrome-extension-rejection-lint <extension-directory>
+The one-liner, no install needed:
+  npx webstore-lint <extension-directory>
 
 Policy data pulled ${POLICY.datasetPulledAt}. Enforcement of the ${POLICY.enforcedFrom} updates:
 ${POLICY.enforcementQuote}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "webstore-lint",
-  "version": "1.0.20",
+  "version": "1.0.21",
   "description": "Check an unpacked Chrome extension against the Chrome Web Store program policies before you submit it. Every finding cites Google's own notification ID and verbatim policy text. Covers the 1 August 2026 policy updates.",
   "keywords": [
     "chrome-extension",