@solongate/proxy 0.82.54 → 0.82.55

package/hooks/guard.bundled.mjs

@@ -6536,7 +6536,7 @@ import { resolve, join, dirname, isAbsolute } from "node:path";
 import { homedir } from "node:os";
 import { gunzipSync } from "node:zlib";
 import { createHash } from "node:crypto";
-var HOOK_VERSION = 46;
+var HOOK_VERSION = 47;
 function localLogsOnly(security) {
   if (security && typeof security === "object") {
     const l = security.localLogs;
@@ -7064,9 +7064,17 @@ var TAMPER_BASENAMES = [
   "guard.mjs",
   "audit.mjs",
   "stop.mjs",
+  "shield.mjs",
   "policy.json",
-  ".policy-cache.json",
-  ".pi-config-cache.json",
+  // Prefixes (substring match) so per-agent runtime state can't be deleted or
+  // rewritten via a shell command either — `.policy-cache-<agent>.json`,
+  // `.ratelimit-<agent>.json`, `.opa-wasm-<agent>.json`. Editing these could
+  // otherwise flip enforcement off until the next cloud refresh; deleting just
+  // forces a refetch, but neither should be reachable from an agent tool call.
+  ".policy-cache",
+  ".ratelimit-",
+  ".opa-wasm-",
+  ".pi-config-cache",
   "cloud-guard.json",
   // Customer install: DB and wizard exe
   "solongate.db",

package/hooks/guard.mjs

@@ -32,7 +32,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 = 46;
+const HOOK_VERSION = 47;
 
 // True when local log storage is ON. In that mode logs are kept LOCAL ONLY and
 // nothing is sent to the cloud audit log.
@@ -799,9 +799,15 @@ const TAMPER_PROTECTED_GLOBS = [
   '**' + TAMPER_INSTALL + '/setup.sh',
 ];
 const TAMPER_BASENAMES = [
-  'guard.mjs', 'audit.mjs', 'stop.mjs',
-  'policy.json', '.policy-cache.json',
-  '.pi-config-cache.json', 'cloud-guard.json',
+  'guard.mjs', 'audit.mjs', 'stop.mjs', 'shield.mjs',
+  'policy.json',
+  // Prefixes (substring match) so per-agent runtime state can't be deleted or
+  // rewritten via a shell command either — `.policy-cache-<agent>.json`,
+  // `.ratelimit-<agent>.json`, `.opa-wasm-<agent>.json`. Editing these could
+  // otherwise flip enforcement off until the next cloud refresh; deleting just
+  // forces a refetch, but neither should be reachable from an agent tool call.
+  '.policy-cache', '.ratelimit-', '.opa-wasm-', '.pi-config-cache',
+  'cloud-guard.json',
   // Customer install: DB and wizard exe
   'solongate.db', 'solongate.exe',
 ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solongate/proxy",
-  "version": "0.82.54",
+  "version": "0.82.55",
   "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": {