@solongate/proxy 0.83.26 → 0.83.27

package/hooks/guard.bundled.mjs

@@ -6579,7 +6579,7 @@ function sweepLegacyFlagDir() {
   } catch {
   }
 }
-var HOOK_VERSION = 80;
+var HOOK_VERSION = 81;
 var SG_REFRESH_ARG = process.argv.includes("--sg-refresh-policy");
 var SG_STDIN = SG_REFRESH_ARG ? "" : (() => {
   try {
@@ -6588,6 +6588,13 @@ var SG_STDIN = SG_REFRESH_ARG ? "" : (() => {
     return "";
   }
 })();
+var SG_ORIGIN_MS = (() => {
+  try {
+    return Math.round(performance.timeOrigin);
+  } catch {
+    return Date.now();
+  }
+})();
 function sgGuardCandidates() {
   const out = [];
   if (process.env.SOLONGATE_GUARD_BIN)
@@ -6629,6 +6636,14 @@ function sgTryGoGuard() {
       r = spawnSync(bin, process.argv.slice(2), {
         input: SG_STDIN,
         encoding: "utf-8",
+        // The binary writes the eval record the audit hook reads back, so it is
+        // the one reporting this call's guard time — and from inside a process
+        // that was spawned partway through the work, it can only see its own
+        // share of it. Node's boot, this file's parse, the fd 0 read and the
+        // version probe above are all already spent by the time it starts.
+        // Handing it the origin is what lets the number it reports be the whole
+        // hook instead of the last two milliseconds of it.
+        env: { ...process.env, SOLONGATE_HOOK_ORIGIN_MS: String(SG_ORIGIN_MS) },
         // Well past every network call the guard makes. A binary still running
         // at this point is not going to produce an answer worth waiting for.
         timeout: 1e4
@@ -8554,7 +8569,7 @@ if (!REFRESH_MODE) {
       allowTool();
       return;
     }
-    const _evalStart = Date.now();
+    const _evalStart = SG_ORIGIN_MS;
     try {
       const raw = JSON.parse(input);
       if (process.env.SOLONGATE_DEBUG) {

package/hooks/guard.mjs

@@ -82,7 +82,7 @@ import { createHash } from 'node:crypto';
 // the installed hook self-updates when the cloud version is higher (see
 // maybeSelfUpdate). This is what makes guard fixes propagate without a manual
 // reinstall — the same trust model as the OPA WASM this hook already runs.
-const HOOK_VERSION = 80;
+const HOOK_VERSION = 81;
 
 // ── The Go guard, when there is one and it is the right one ──────────────────
 //
@@ -126,6 +126,24 @@ const SG_STDIN = SG_REFRESH_ARG ? '' : (() => {
   try { return readFileSync(0, 'utf-8'); } catch { return ''; }
 })();
 
+// When this process began, as epoch milliseconds — the instant every reported
+// guard time is measured from.
+//
+// `performance.timeOrigin` is stamped before Node's bootstrap runs, so a
+// duration taken from it includes the interpreter coming up and this file being
+// parsed. That is not an accounting nicety: those two are the MAJORITY of what a
+// tool call pays for enforcement. Starting the clock further down (which is what
+// `Date.now()` at the top of the async body did) left them outside the window
+// and made the audit log report ~1ms for a call that really cost tens of them —
+// a number no process on a real machine can achieve, and one that quietly turned
+// the latency column into fiction.
+//
+// What is still NOT in it: the client's own fork/exec of node, which happens
+// before this process exists and which nothing running inside it can observe.
+const SG_ORIGIN_MS = (() => {
+  try { return Math.round(performance.timeOrigin); } catch { return Date.now(); }
+})();
+
 // Where a binary may legitimately live, in the order they are trusted.
 //
 // The env override is first so a build can be pointed at without reinstalling.
@@ -180,6 +198,14 @@ function sgTryGoGuard() {
       r = spawnSync(bin, process.argv.slice(2), {
         input: SG_STDIN,
         encoding: 'utf-8',
+        // The binary writes the eval record the audit hook reads back, so it is
+        // the one reporting this call's guard time — and from inside a process
+        // that was spawned partway through the work, it can only see its own
+        // share of it. Node's boot, this file's parse, the fd 0 read and the
+        // version probe above are all already spent by the time it starts.
+        // Handing it the origin is what lets the number it reports be the whole
+        // hook instead of the last two milliseconds of it.
+        env: { ...process.env, SOLONGATE_HOOK_ORIGIN_MS: String(SG_ORIGIN_MS) },
         // Well past every network call the guard makes. A binary still running
         // at this point is not going to produce an answer worth waiting for.
         timeout: 10000,
@@ -2620,7 +2646,12 @@ if (!REFRESH_MODE) { input += SG_STDIN; }
     allowTool();
     return;
   }
-  const _evalStart = Date.now();
+  // NOT `Date.now()`. Every `Date.now() - _evalStart` below becomes an
+  // evaluation_time_ms in the audit log — the number the dashboard, the dataroom
+  // and the TUI print as what this call paid to be guarded. Measured from here
+  // it excluded Node's boot and this file's parse, which is most of the cost,
+  // and reported ~1ms for a hook that was really taking tens. See SG_ORIGIN_MS.
+  const _evalStart = SG_ORIGIN_MS;
   try {
     const raw = JSON.parse(input);
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solongate/proxy",
-  "version": "0.83.26",
+  "version": "0.83.27",
   "description": "AI tool security proxy: protect any AI tool server with customizable policies, path/command constraints, rate limiting, and audit logging. No code changes required.",
   "type": "module",
   "bin": {
@@ -61,12 +61,12 @@
     "node": ">=20.0.0"
   },
   "optionalDependencies": {
-    "@solongate/guard-linux-x64": "0.83.26",
-    "@solongate/guard-linux-arm64": "0.83.26",
-    "@solongate/guard-darwin-x64": "0.83.26",
-    "@solongate/guard-darwin-arm64": "0.83.26",
-    "@solongate/guard-win32-x64": "0.83.26",
-    "@solongate/guard-win32-arm64": "0.83.26"
+    "@solongate/guard-linux-x64": "0.83.27",
+    "@solongate/guard-linux-arm64": "0.83.27",
+    "@solongate/guard-darwin-x64": "0.83.27",
+    "@solongate/guard-darwin-arm64": "0.83.27",
+    "@solongate/guard-win32-x64": "0.83.27",
+    "@solongate/guard-win32-arm64": "0.83.27"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.26.0",