mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-31 14:06:50 +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.3 KiB
TypeScript
Executable File
30 lines
1.3 KiB
TypeScript
Executable File
#!/usr/bin/env -S bun --no-env-file --config=/dev/null
|
|
/**
|
|
* gstack-gbrain-supabase-provision — Supabase Management API wrapper for
|
|
* /setup-gbrain path 2a (auto-provision). Thin entry: all logic lives in
|
|
* lib/gbrain-supabase-provision.ts so tests can drive it in-process with
|
|
* injected fetch/env/sleep instead of spawning a process per test.
|
|
*
|
|
* Rewritten from bash to TypeScript; filename and exec semantics unchanged —
|
|
* callers shell out to this path and the bun shebang resolves at runtime
|
|
* (same pattern as bin/gstack-gbrain-detect). CLI surface, stdout/stderr
|
|
* shapes, env handling (SUPABASE_ACCESS_TOKEN / DB_PASS / SUPABASE_API_BASE),
|
|
* and exit codes are unchanged; run --help for the full contract.
|
|
*
|
|
* Egress receipts stay fail-closed at the API-call layer (sink
|
|
* "supabase-provision", receipt-before-send) — see the module header.
|
|
*/
|
|
|
|
import { runProvision } from '../lib/gbrain-supabase-provision';
|
|
|
|
// exitCode, not process.exit(): exit() drops pending stdout writes, which
|
|
// truncates piped JSON / large listings; setting exitCode lets writes drain
|
|
// and the process exit naturally.
|
|
runProvision(process.argv.slice(2)).then(
|
|
(code) => { process.exitCode = code; },
|
|
(error) => {
|
|
process.stderr.write(`gstack-gbrain-supabase-provision: ${(error as Error)?.stack ?? error}\n`);
|
|
process.exitCode = 1;
|
|
},
|
|
);
|