mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-31 22:14:25 +01:00
* security: isolate every gstack Bun entry point from the audited checkout's .env and bunfig.toml Bun auto-loads .env, .env.local and .env.<NODE_ENV> from its cwd and runs a cwd bunfig.toml preload before the program starts. gstack runs inside the repo it audits, so a committed .env could steer state roots, the claude binary or spend caps, and a bunfig preload ran arbitrary code in every bin and hook. Every bun shebang, shell and skill caller, TypeScript spawn and compiled build now disables both (--no-env-file --config=/dev/null, bunIsolationArgs(), --no-compile-autoload-dotenv/bunfig), with a ratchet and hostile-fixture regressions. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: name the directly executed scripts in the isolation ratchet Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: follow the isolation flags in touchfiles, copy lists, recipe assertions and the harness pin Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: keep browse/src/bun-child-config.ts unchanged so the native cookie qualification still binds Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(windows): the empty bunfig outlives its process so the timeline hook's detached repair child can read it Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * v1.91.159.0 security: gstack's Bun entry points ignore the audited repo's .env and bunfig.toml (S1) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: plan-mode render pattern accepts the isolation flags Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
30 lines
1.2 KiB
TypeScript
Executable File
30 lines
1.2 KiB
TypeScript
Executable File
#!/usr/bin/env -S bun --no-env-file --config=/dev/null
|
|
/**
|
|
* gstack-greptile-early — /ship's early Greptile review (detect, consent, open, wait).
|
|
*
|
|
* gstack-greptile-early detect
|
|
* gstack-greptile-early consent yes|no
|
|
* gstack-greptile-early open --base <branch> --title-file <file> [--ready] [--confirm <token>]
|
|
* gstack-greptile-early wait <pr-number> --since <epoch-seconds>
|
|
*
|
|
* On by default when the repo uses Greptile; `gstack-config set
|
|
* ship_greptile_early false` turns it off. Logic: lib/greptile-early.ts.
|
|
*/
|
|
import * as path from "path";
|
|
import { spawnSync } from "child_process";
|
|
import { runGreptileEarly } from "../lib/greptile-early";
|
|
|
|
process.exitCode = runGreptileEarly(process.argv.slice(2), {
|
|
run(cmd, args, input) {
|
|
const r = spawnSync(cmd, args, { input: input ?? "", encoding: "utf8", timeout: 120_000, maxBuffer: 16 * 1024 * 1024 });
|
|
return { status: r.status ?? 1, stdout: r.stdout ?? "", stderr: r.stderr ?? (r.error ? String(r.error) : "") };
|
|
},
|
|
vars: process.env,
|
|
binDir: path.resolve(import.meta.dir),
|
|
bun: process.execPath,
|
|
now: () => Date.now(),
|
|
sleep: (ms) => Bun.sleepSync(ms),
|
|
out: (t) => process.stdout.write(t),
|
|
err: (t) => process.stderr.write(t),
|
|
});
|