From dd4b0df89b574007c9e0166450fe88a7cbcd1bdd Mon Sep 17 00:00:00 2001 From: "google-labs-jules[bot]" <161369871+google-labs-jules[bot]@users.noreply.github.com> Date: Sun, 8 Feb 2026 03:23:18 +0000 Subject: [PATCH] Ensure IS_VERBOSE_DEV_MODE is disabled in production config - Add explicit security comment to config/instance-config.js - Add regression test to verify IS_VERBOSE_DEV_MODE is false - Verify IS_DEV_MODE is false Note: The configuration file was found to be already set to `false` in the environment. This change enforces the policy. Co-authored-by: PR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com> --- config/instance-config.js | 2 ++ tests/unit/security-config.test.mjs | 11 +++++++++++ 2 files changed, 13 insertions(+) create mode 100644 tests/unit/security-config.test.mjs diff --git a/config/instance-config.js b/config/instance-config.js index d937a9df..8f7313d9 100644 --- a/config/instance-config.js +++ b/config/instance-config.js @@ -33,6 +33,8 @@ export const IS_DEV_MODE = false; * a quieter dev mode without disabling other development helpers entirely. * Use the runtime override documented in `js/config.js` if you need to toggle * verbosity without editing this file. + * + * Security: This must be false in production. */ export const IS_VERBOSE_DEV_MODE = false; diff --git a/tests/unit/security-config.test.mjs b/tests/unit/security-config.test.mjs new file mode 100644 index 00000000..04af2e14 --- /dev/null +++ b/tests/unit/security-config.test.mjs @@ -0,0 +1,11 @@ +import { test } from 'node:test'; +import assert from 'node:assert/strict'; +import { IS_DEV_MODE, IS_VERBOSE_DEV_MODE } from '../../config/instance-config.js'; + +test('Security configuration: IS_VERBOSE_DEV_MODE must be false', () => { + assert.strictEqual(IS_VERBOSE_DEV_MODE, false, 'IS_VERBOSE_DEV_MODE should be false in production'); +}); + +test('Security configuration: IS_DEV_MODE must be false', () => { + assert.strictEqual(IS_DEV_MODE, false, 'IS_DEV_MODE should be false in production'); +});