@pify/shell-background 0.4.0 → 0.4.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pify/shell-background",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Long-running bash goes async: background: true launches detached, and any command still running after 30s auto-backgrounds and delivers its result when it finishes",
   "keywords": [
     "pi-package",

package/src/registry.ts

@@ -44,7 +44,8 @@ export class JobRegistry {
 
   constructor(baseDir: string) {
     this.baseDir = baseDir;
-    mkdirSync(join(baseDir, "logs"), { recursive: true });
+    // Logs and sidecars carry command output and cwd paths: the user's eyes only.
+    mkdirSync(join(baseDir, "logs"), { recursive: true, mode: 0o700 });
   }
 
   /** The directory this registry's sidecars and logs live under. */
@@ -93,7 +94,7 @@ export class JobRegistry {
     try {
       const file = join(this.baseDir, `${job.id}.json`);
       const tmp = `${file}.${process.pid}.tmp`;
-      writeFileSync(tmp, JSON.stringify(job));
+      writeFileSync(tmp, JSON.stringify(job), { mode: 0o600 });
       renameSync(tmp, file);
     } catch {
       // A registry we cannot persist still works for the live session.

package/src/spawn.ts

@@ -40,7 +40,9 @@ export function spawnToFile(
   logPath: string,
 ): Spawned {
   // Append so a re-attach or racing read never clips output already written.
-  const out = createWriteStream(logPath, { flags: "a" });
+  // Command output can carry private data, so the log is readable by the user
+  // only (pi 1.0.3 does the same for its own output files; a no-op on Windows).
+  const out = createWriteStream(logPath, { flags: "a", mode: 0o600 });
   // A write stream with no 'error' listener turns any disk error (ENOSPC,
   // EACCES) or a stray write-after-end into an uncaught exception that takes the
   // whole pi host down. Losing a log line is survivable; crashing the host is