pi-server 0.1.0

package/README.md

@@ -0,0 +1,29 @@
+# pi-server
+
+> **This is a namespace reservation package.** Install [`@marcfargas/pi-server`](https://www.npmjs.com/package/@marcfargas/pi-server) for the real package.
+
+## Why does this package exist?
+
+This unscoped wrapper exists to prevent supply-chain attacks. Without it, a
+malicious actor could publish a package named `pi-server` on npm. Anyone who
+then ran `npx pi-server` without having installed the scoped package first
+would unknowingly execute the attacker's code.
+
+By holding this name, `npx pi-server` safely delegates to the real
+`@marcfargas/pi-server` package.
+
+## Usage
+
+```bash
+# These all work:
+npx pi-server serve --provider google --model gemini-2.5-flash
+npx @marcfargas/pi-server serve --provider google --model gemini-2.5-flash
+
+# Or install globally:
+npm install -g pi-server
+pi-server serve --port 3333
+```
+
+## License
+
+MIT

package/cli.js

@@ -0,0 +1,5 @@
+#!/usr/bin/env node
+// Thin wrapper — delegates to @marcfargas/pi-server.
+// This unscoped package exists to prevent supply-chain attacks via npm name
+// squatting. The real implementation lives in @marcfargas/pi-server.
+import("@marcfargas/pi-server/cli");

package/package.json

@@ -0,0 +1,19 @@
+{
+  "name": "pi-server",
+  "version": "0.1.0",
+  "description": "Namespace reservation for @marcfargas/pi-server. This package exists solely to prevent supply-chain attacks via npm name squatting. Install @marcfargas/pi-server for the real package.",
+  "type": "module",
+  "bin": {
+    "pi-server": "./cli.js",
+    "pi-serve": "./cli.js"
+  },
+  "dependencies": {
+    "@marcfargas/pi-server": "0.1.0"
+  },
+  "license": "MIT",
+  "author": "Marc Fargas",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/marcfargas/pi-server"
+  }
+}