@everme/cli 0.1.0-beta.3 → 0.1.1

package/README.md

@@ -1,13 +1,13 @@
 # @everme/cli
 
-npm-distributed installer for [EverMe CLI](https://github.com/alwaysday1/everme). Detects your platform on install, downloads the matching pre-built binary from GitHub Releases, verifies its SHA-256 checksum, and exposes it as the `evercli` command.
+npm-distributed installer for [EverMe CLI](https://github.com/EverMind-AI/EverMe-CLI). Detects your platform on install, downloads the matching pre-built binary from GitHub Releases, verifies its SHA-256 checksum, and exposes it as the `evercli` command.
 
 ```bash
-npm install -g @everme/cli@beta
+npm install -g @everme/cli
 evercli --help
 
 # or, no install
-npx @everme/cli@beta --version
+npx @everme/cli --version
 ```
 
 ## What this package does
@@ -15,7 +15,7 @@ npx @everme/cli@beta --version
 `@everme/cli` is a thin Node-side installer + runner; the actual CLI is a pre-compiled binary downloaded on first install. On `npm install`:
 
 1. Detect platform / arch (darwin/linux/windows × amd64/arm64)
-2. Download the matching archive from `https://github.com/alwaysday1/everme/releases/download/v<version>/evercli_<os>_<arch>.{tar.gz|zip}`
+2. Download the matching archive from `https://github.com/EverMind-AI/EverMe-CLI/releases/download/v<version>/evercli_<os>_<arch>.{tar.gz|zip}`
 3. Verify SHA-256 against the `sha256sums.txt` shipped inside this npm package
 4. Extract and place the binary under the package's `bin/` directory
 5. The `evercli` shim (`scripts/run.js`) execs that binary with your args
@@ -26,7 +26,7 @@ If `postinstall` was skipped (some `npx` flows, restricted CI), the installer ru
 
 The installer tries download sources in this order:
 
-1. `https://github.com/alwaysday1/everme/releases/...` (canonical)
+1. `https://github.com/EverMind-AI/EverMe-CLI/releases/...` (canonical)
 2. The npm registry's binary mirror path (`<registry>/-/binary/everme-cli/...`), if your `npm_config_registry` is non-default
 3. `https://registry.npmmirror.com/-/binary/everme-cli/...` (always tried as final fallback)
 
@@ -41,11 +41,6 @@ export EVERCLI_API_BASE_URL=https://memory.acme-internal.com
 evercli auth login
 ```
 
-## Release channels
-
-- `@everme/cli@beta` — pre-release builds
-- `@everme/cli@latest` — stable releases
-
 ## License
 
 Apache-2.0.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everme/cli",
-  "version": "0.1.0-beta.3",
+  "version": "0.1.1",
   "description": "EverMe CLI — npm wrapper that downloads and runs the platform-native evercli binary on first use.",
   "license": "Apache-2.0",
   "bin": {
@@ -38,14 +38,14 @@
     "ai",
     "agent"
   ],
-  "homepage": "https://everme.ai",
+  "homepage": "https://everme.evermind.ai",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/alwaysday1/everme.git",
+    "url": "git+https://github.com/EverMind-AI/EverMe-CLI.git",
     "directory": "plugins/cli"
   },
   "bugs": {
-    "url": "https://github.com/alwaysday1/everme/issues"
+    "url": "https://github.com/EverMind-AI/EverMe-CLI/issues"
   },
   "publishConfig": {
     "access": "public",

package/scripts/install.js

@@ -6,8 +6,8 @@
  * postinstall hook for @everme/cli — downloads, verifies, and extracts the
  * platform-native evercli binary into <pkg>/bin.
  *
- * Conventions match this monorepo's existing goreleaser config and shell
- * installer (cli/.goreleaser.yml, cli/scripts/install.sh):
+ * Conventions match this monorepo's existing goreleaser config
+ * (cli/.goreleaser.yml):
  *
  *   tag      cli/vX.Y.Z
  *   archive  evercli_<os>_<arch>.tar.gz   (Unix)
@@ -25,12 +25,8 @@ const os = require("os");
 const crypto = require("crypto");
 const { execFileSync } = require("child_process");
 
-// Keep prerelease suffix (e.g. "0.1.0-beta.1") intact — GoReleaser tags
-// match package.json version verbatim, so stripping after `-` would build
-// TAG = cli/v0.1.0 for a 0.1.0-beta.1 publish and 404 against the real
-// cli/v0.1.0-beta.1 release.
 const VERSION = require("../package.json").version;
-const REPO = "alwaysday1/everme";
+const REPO = "EverMind-AI/EverMe-CLI";
 const NAME = "evercli";
 
 // Allowlist gates the *initial* request URL. curl --location follows redirects
@@ -182,16 +178,24 @@ function extractZipWindows(archivePath, destDir) {
 
 /**
  * Look up the SHA256 checksum for the archive from sha256sums.txt that ships
- * inside this npm package. If the file is missing (e.g. local dev pack), warn
- * and skip — the goreleaser CI is expected to copy sha256sums.txt before
- * publishing.
+ * inside this npm package. sha256sums.txt is listed in package.json::files,
+ * so a real `npm install` will always include it. A missing file is either
+ * a tampered tarball or a broken publish — in both cases skipping the check
+ * defeats the integrity model, so we hard-fail instead of warning.
+ *
+ * The workspace dev-install path is already short-circuited above
+ * (`__dirname.includes("/node_modules/")`), so this branch is only ever
+ * reached for installs that MUST verify.
  */
 function getExpectedChecksum(archive, checksumsDir) {
   const dir = checksumsDir || path.join(__dirname, "..");
   const checksumsPath = path.join(dir, "sha256sums.txt");
   if (!fs.existsSync(checksumsPath)) {
-    console.error("[WARN] sha256sums.txt not found, skipping checksum verification");
-    return null;
+    throw new Error(
+      `[SECURITY] sha256sums.txt missing at ${checksumsPath}; refusing to install ` +
+        `an unverified binary. The file ships with the npm package — its absence ` +
+        `indicates tampering or a broken release.`,
+    );
   }
   const content = fs.readFileSync(checksumsPath, "utf8");
   for (const line of content.split("\n")) {
@@ -207,8 +211,34 @@ function getExpectedChecksum(archive, checksumsDir) {
   throw new Error(`Checksum entry not found for ${archive}`);
 }
 
+/**
+ * Defends against zip-slip: an archive can ship `evercli` as a symlink to
+ * `/etc/passwd` (or any path outside tmpDir). copyFileSync follows symlinks,
+ * so without this check the extracted "binary" we ship to <pkg>/bin could
+ * be sourced from anywhere. lstat catches the symlink case (we reject non-
+ * regular files); realpath resolves what the path actually points at and we
+ * assert it stays within tmpDir.
+ */
+function assertInsideDir(dir, candidate) {
+  const stat = fs.lstatSync(candidate);
+  if (!stat.isFile()) {
+    throw new Error(
+      `[SECURITY] Extracted entry is not a regular file (mode=${stat.mode.toString(8)}); ` +
+        `refusing to install. Path: ${candidate}`,
+    );
+  }
+  const realDir = fs.realpathSync(dir);
+  const realCandidate = fs.realpathSync(candidate);
+  const sep = path.sep;
+  if (realCandidate !== realDir && !realCandidate.startsWith(realDir + sep)) {
+    throw new Error(
+      `[SECURITY] Extracted path escapes archive root: ${realCandidate} not under ${realDir}`,
+    );
+  }
+  return realCandidate;
+}
+
 function verifyChecksum(archivePath, expectedHash) {
-  if (expectedHash === null) return;
   // Stream to keep RSS constant; archives can be ~10MB+.
   const hash = crypto.createHash("sha256");
   const fd = fs.openSync(archivePath, "r");
@@ -260,11 +290,27 @@ function install() {
     if (isWindows) {
       extractZipWindows(archivePath, tmpDir);
     } else {
-      execFileSync("tar", ["-xzf", archivePath, "-C", tmpDir], { stdio: "ignore" });
+      // --no-same-owner / --no-same-permissions matter when postinstall
+      // runs as root (e.g. system-wide npm install) — without them, a
+      // hostile archive could set setuid/world-writable modes on the
+      // extracted binary. The flags are accepted by both GNU tar (Linux)
+      // and BSD tar (macOS). Modern tar already rejects ".." paths by
+      // default; the post-extraction realpath check below is the second
+      // line of defense against zip-slip via symlinks.
+      execFileSync(
+        "tar",
+        [
+          "-xzf", archivePath,
+          "-C", tmpDir,
+          "--no-same-owner",
+          "--no-same-permissions",
+        ],
+        { stdio: "ignore" },
+      );
     }
 
     const binaryName = NAME + (isWindows ? ".exe" : "");
-    const extractedBinary = path.join(tmpDir, binaryName);
+    const extractedBinary = assertInsideDir(tmpDir, path.join(tmpDir, binaryName));
     fs.copyFileSync(extractedBinary, dest);
     fs.chmodSync(dest, 0o755);
     console.log(`${NAME} v${VERSION} installed successfully`);
@@ -331,5 +377,6 @@ module.exports = {
   getExpectedChecksum,
   verifyChecksum,
   assertAllowedHost,
+  assertInsideDir,
   resolveMirrorUrls,
 };

package/scripts/run.js

@@ -22,6 +22,7 @@
 
 const { execFileSync } = require("child_process");
 const fs = require("fs");
+const os = require("os");
 const path = require("path");
 
 const NAME = "evercli";
@@ -83,6 +84,17 @@ if (args[0] === "install") {
   try {
     execFileSync(bin, args, { stdio: "inherit" });
   } catch (e) {
-    process.exit(e.status || 1);
+    // Preserve the child's exit semantics. execFileSync throws an Error
+    // whose `.status` is the exit code OR null when the child was killed
+    // by a signal (`.signal` is set instead). Mapping signal → 128+N
+    // matches POSIX shell convention so callers (CI, parent shells) can
+    // distinguish SIGINT (130) from a clean exit 1.
+    if (typeof e.status === "number") {
+      process.exit(e.status);
+    }
+    if (e.signal && os.constants.signals && os.constants.signals[e.signal]) {
+      process.exit(128 + os.constants.signals[e.signal]);
+    }
+    process.exit(1);
   }
 }

package/sha256sums.txt

@@ -1,6 +1,6 @@
-ab0513a3c000d3dfa06f16ebd3289820ef52970d1262c585ffcc8d5b4e777fe0  evercli_darwin_amd64.tar.gz
-f41616c6d0c6fb8c2ab5271bb4cb3f8e757db82d8802f45e446d4bd64a653c32  evercli_darwin_arm64.tar.gz
-7b3f8f2c48e197a21941f34e39d61c56bb394471c3ce50bc6718bd79361a22d9  evercli_linux_amd64.tar.gz
-964b85a6cf4708eaa625178c9f52dcc04a17f53b6a7e0176a67b12762e293f88  evercli_linux_arm64.tar.gz
-6608dd0a297868d91a5c91d1941bddeb39a11afa3f9d747a45495dce85527ab0  evercli_windows_amd64.zip
-de33a17dbba12f03a4bd729ab4976635b97d3c3632e56796e83515ebe54c229c  evercli_windows_arm64.zip
+ebe4459a6efeaeb7fab2d210208ff64b3d787338fad66690add284eff0442047  evercli_darwin_amd64.tar.gz
+285c4d77d69b4850a1b84156b4196a0800af8ddb16428558414c6ceb9f91dda6  evercli_darwin_arm64.tar.gz
+8ac26b56ed87875764c7cf84567e8123596565d33459a2278f95e00070db8251  evercli_linux_amd64.tar.gz
+8f2d75be861849f1c5bb8bbfb8437b3106a4ed48c2f40d268b4b21d5ea277cb7  evercli_linux_arm64.tar.gz
+6477aa4da68d15d8a2bba1bcdb6e39f3122215319cba4e44c60ac91e644fcbe2  evercli_windows_amd64.zip
+dc17458b21b1e26958d9946506deeae40d8f4b4885beea926a95fd9487a26b58  evercli_windows_arm64.zip