No entries match these filters. Clear filters
@lavamoat/react-native-lockdown@3.0.0
Nov 18, 2026
·
issue 144
LavaMoat's react-native-lockdown adds @endo/parser-pipeline support for Node.js parsing︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSIONnpm git
npm
copy
$ npm install lavamoat@3.0.0
git
copy
$ git clone --branch @lavamoat/react-native-lockdown@3.0.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout @lavamoat/react-native-lockdown@3.0.0
signed build provenance · checked 19 Nov
└──▷ BREAKING ON UPGRADE
! The SES upgrade may introduce regressions in Hermes; this release is versioned as major (3.0.0) out of caution — test Hermes-based React Native builds before upgrading.
@lavamoat/allow-scripts@5.1.1
Nov 18, 2026
·
issue 144
LavaMoat allow-scripts adds a check command to warn in CI when the allow-list needs updating, and now pins install scripts to exact versions︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSIONnpm git
npm
copy
$ npm install lavamoat@5.1.1
git
copy
$ git clone --branch @lavamoat/allow-scripts@5.1.1 https://github.com/LavaMoat/LavaMoat.git
$ git checkout @lavamoat/allow-scripts@5.1.1
signed build provenance · checked 19 Nov
└──▷ TRY IT
Run in CI to detect when an install script has changed version and the allow-list is out of date, failing the pipeline before a stale config silently applies.
copy
$ npx @lavamoat/allow-scripts check
Add a check command to warn in CI when the allow-scripts configuration needs to be updated, catching stale allow-lists before they silently permit or block scripts.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Install scripts are now pinned to exact versions by default, so a dependency upgrade that swaps in a new install script is blocked until the allow-list is explicitly updated. Not checked yet
Add a check command to warn in CI when the allow-scripts configuration needs to be updated, catching stale allow-lists before they silently permit or block scripts.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! allow-scripts no longer matches a lower version with the allowed version — a pinned entry for an older version of a package will not cover a newer one.! allow-scripts now defaults to pinning versions; existing configurations require a migration action to continue working.! Node.js v18 is no longer supported.
preinstall-always-fail-v3.0.2
Nov 16, 2026
·
issue 142
└──▷ GET THIS VERSION
copy
$ git clone --branch preinstall-always-fail-v3.0.2 https://github.com/LavaMoat/LavaMoat.git
$ git checkout preinstall-always-fail-v3.0.2
LavaMoat harden adds yarn plugin and npm PATH overrides to block more classes of bin script confusion︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSION
copy
$ git clone --branch harden-v0.9.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout harden-v0.9.0
LavaMoat harden's runner now accepts new bins that are not collisions with existing entries.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet LavaMoat harden now falls back on the detected package manager more eagerly when no explicit manager is configured. Not checked yet
2 more in Everything
Webpack v3.0 introduces new @endo/parser-pipeline for node and updates the generatePolicy() API return structure.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v3.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v3.0.0
└──▷ USE IT
Consume the updated policy object from generatePolicy in your node code.
code
copy
const { policy, hasWarnings } = await generatePolicy();
Write a policy to disk using the new dedicated function introduced in this release.
code
copy
import { writePolicy } from '@lavamoat/node';
writePolicy(policy);
node: use @endo/parser-pipeline Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! generatePolicy() no longer accepts write/writableFs options.
LavaMoat v2.0.0 expands LavaMoatPolicy.include and other breaking changes
└──▷ GET THIS VERSION
copy
$ git clone --branch types-v2.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout types-v2.0.0
Expands the LavaMoatPolicy.include field to allow more granular policy matching. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The LavaMoatPolicy.include structure has been expanded; existing configs may need updates.
LavaMoat types v2.0.0 expands LavaMoatPolicy.include with a breaking change to its shape.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSION
copy
$ git clone --branch types-v2.0.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout types-v2.0.0
Expands LavaMoatPolicy.include to support a wider set of values in the LavaMoat policy type definitions.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The shape of LavaMoatPolicy.include has changed — existing code typed against the old LavaMoatPolicy.include definition may no longer type-check and will require updates.
react-native-lockdown v3.0.0 introduces writePolicy import and API changes to generatePolicy() via @endo/parser-pipeline
└──▷ GET THIS VERSION
copy
$ git clone --branch react-native-lockdown-v3.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout react-native-lockdown-v3.0.0
└──▷ USE IT
Migrate programmatic policy generation to capture warnings and separate write logic.
shell
copy
const { generatePolicy, writePolicy } = require('@lavamoat/node');
async function main() {
const { policy, hasWarnings } = await generatePolicy();
if (hasWarnings) console.warn('Policy generation had warnings');
await writePolicy(policy);
}
Introduces writePolicy import from @lavamoat/node for explicit policy disk writes, separating concerns from generation. Not checked yet Switches internal parsing to use @endo/parser-pipeline. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! generatePolicy() now resolves with { policy: LavaMoatPolicy, hasWarnings: boolean } instead of a LavaMoatPolicy directly; destructure policy from the result.! generatePolicy() no longer accepts write or writableFs options.
react-native-lockdown-v3.0.0
Sep 25, 2026
·
issue 085
LavaMoat react-native-lockdown v3.0.0 adopts @endo/parser-pipeline and splits generatePolicy() into separate generate and write steps︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSION
copy
$ git clone --branch react-native-lockdown-v3.0.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout react-native-lockdown-v3.0.0
Adds writePolicy export from @lavamoat/node to write a policy to disk, separate from generatePolicy() .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Switches @lavamoat/node to use @endo/parser-pipeline for module parsing. Not checked yet
Adds writePolicy export from @lavamoat/node to write a policy to disk, separate from generatePolicy() .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! generatePolicy() in @lavamoat/node now resolves with { policy: LavaMoatPolicy, hasWarnings: boolean } instead of a bare LavaMoatPolicy; callers must destructure policy from the result.! generatePolicy() in @lavamoat/node no longer accepts write or writableFs options and no longer writes policy to disk; use the new writePolicy import from @lavamoat/node instead.
LavaMoat v2 adds location-based includes and changes generatePolicy() API
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v2.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v2.0.0
Adds support for location-based includes in @lavamoat/node Not checked yet Exports a new writePolicy function from @lavamoat/node for writing policies to disk Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! generatePolicy() no longer accepts write or writableFs options! generatePolicy() no longer writes policy to disk automatically; use the new writePolicy function instead! The return value of generatePolicy() has changed: destructure policy from the resolved object { policy, hasWarnings }
LavaMoat Node 2.0 adds location-based policy includes, a new writePolicy export, and switches to @endo/parser-pipeline.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v2.0.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout node-v2.0.0
└──▷ BREAKING ON UPGRADE
! generatePolicy() now resolves with { policy: LavaMoatPolicy, hasWarnings: boolean } instead of a bare LavaMoatPolicy — callers must destructure policy from the resolved object.! generatePolicy() no longer accepts write or writableFs options and no longer writes policy to disk; use writePolicy imported from @lavamoat/node instead.
LavaMoat v0.8.0 extends script configs for granular hardening rules.
└──▷ GET THIS VERSION
copy
$ git clone --branch harden-v0.8.0 https://github.com/lavamoat/lavamoat.git
$ git checkout harden-v0.8.0
Extends the scripts configuration block in package.json to allow per-script hardening options such as network and file-system access control. Not checked yet
1 detail in Everything
LavaMoat harden v0.8.0 extends script configs for tighter supply chain control.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSION
copy
$ git clone --branch harden-v0.8.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout harden-v0.8.0
Extends script configs in the harden package, expanding the configuration surface available for controlling how scripts are hardened.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
lavamoat-core-v19.0.0 adds policy override compact function and expanded LavaMoatPolicy.include support
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v19.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v19.0.0
@lavamoat/node generatePolicy() now returns { policy: LavaMoatPolicy, hasWarnings: boolean } instead of resolving directly to LavaMoatPolicy. Not checked yet writePolicy imported from @lavamoat/node replaces the removed write/writableFs options for writing policies to disk. Not checked yet Exposes policy override compact function for use in custom workflows. Not checked yet Supports expanded LavaMoatPolicy.include patterns. Not checked yet
4 details in Everything
└──▷ BREAKING ON UPGRADE
! generatePolicy() no longer accepts write or writableFs options; use the new writePolicy export instead to write policies to disk.! Destructure policy from the object returned by generatePolicy() ; it no longer resolves directly to a LavaMoatPolicy.
lavamoat-core-v19.0.0
Sep 25, 2026
·
issue 085
lavamoat-core v19 expands LavaMoatPolicy.include, exposes policy-override compact function, and adopts @endo/parser-pipeline︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v19.0.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout lavamoat-core-v19.0.0
└──▷ USE IT
Generate a policy and check for warnings before writing it to disk — required migration pattern after the generatePolicy() API change.
javascript
copy
import { generatePolicy, writePolicy } from '@lavamoat/node';
const { policy, hasWarnings } = await generatePolicy({ projectRoot: '.' });
if (hasWarnings) console.warn('Policy generated with warnings');
await writePolicy({ policy, policyPath: './lavamoat/node/policy.json' });
└──▷ BREAKING ON UPGRADE
! generatePolicy() in @lavamoat/node now resolves with { policy: LavaMoatPolicy, hasWarnings: boolean } instead of a bare LavaMoatPolicy — callers must destructure policy from the result.! generatePolicy() no longer accepts write or writableFs options and will not write policy to disk; migrate to writePolicy imported from @lavamoat/node.! LavaMoatPolicy.include has an expanded schema — existing policy files using the previous include format may need to be updated.
webpack-v2.3.0 adds opt-in overwrite flag and captures importScripts references for runtime use
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v2.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v2.3.0
└──▷ TRY IT
Allow a specific build to bypass existing policy restrictions by writing overrides directly.
copy
$ lavamoat --overwrite ./path/to/overrides.json
Adds --overwrite flag to allow policy.json to be overwritten with overrides Not checked yet Webpack integration now captures importScripts references for use in runtime despite scuttling Not checked yet
2 details in Everything
LavaMoat webpack plugin gains a policy-overwrite opt-in flag and scuttling-safe importScripts capture.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v2.3.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout webpack-v2.3.0
Adds opt-in flag to overwrite policy.json with overrides, enabling automated policy regeneration workflows. Not checked yet Captures importScripts reference for use in the webpack runtime even when scuttling is enabled, unblocking Web Worker builds that rely on importScripts. Not checked yet
2 details in Everything
LavaMoat node v1.1.0 introduces the new @lavamoat/harden package.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v1.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v1.1.0
LavaMoat harden v0.7.0 adds JSON output via --json flag and prefix-based scriptsConfig wildcard matching
└──▷ GET THIS VERSION
copy
$ git clone --branch harden-v0.7.0 https://github.com/lavamoat/lavamoat.git
$ git checkout harden-v0.7.0
└──▷ USE IT
Get JSON output from hardening process for CI parsing
shell
copy
npx lavamoat --harden --json
Adds --json option to harden command for machine-readable output Not checked yet Enables prefix-based wildcard matching in the runner scriptsConfig configuration Not checked yet
2 details in Everything
LavaMoat harden adds a --json check option and wildcard prefix matching for runner scriptsConfig
└──▷ GET THIS VERSION
copy
$ git clone --branch harden-v0.7.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout harden-v0.7.0
└──▷ TRY IT
Output harden check results as JSON for ingestion into a CI pipeline or SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. .
copy
$ harden check --json
Adds --json option to the harden check command for machine-readable output. Not checked yet Adds wildcard prefix matching for scriptsConfig entries in the harden runner, allowing glob-style script name patterns. Not checked yet
2 details in Everything
LavaMoat adds scriptsConfig to assign Node.js permission profiles per package.json script, enforcing least-privilege on build, test, and release commands.
└──▷ USE IT
Security-first setup: lock most scripts to the strict profile and carve out explicit exceptions for build and release commands.
package.json
copy
{
"scripts": {
"lint": "eslint .",
"test": "ava",
"build": "vite build",
"release": "node scripts/release.mjs"
},
"scriptsConfig": {
"#default": "lavamoat/scripts.strict.json",
"build": "lavamoat/scripts.loose.json",
"release": "lavamoat/scripts.release.json"
}
}
Allow a composing or highly privileged script to run without any Node.js permission restrictions by pointing it at a null profile.
lavamoat/scripts.null.json
copy
{
"NODE_OPTIONS": {}
}
Adds scriptsConfig key to package.json that maps each script name to a JSON file containing NODE_OPTIONS permission flags, letting you assign distinct Node.js permission profiles to lint, test, build, release, and other scripts individually. Not checked yet Introduces #default key in scriptsConfig to set a fallback permission profile for all scripts not explicitly listed, supporting both security-first (strict default) and compatibility-first (no default) strategies. Not checked yet Ships two starter permission profiles — lavamoat/scripts.strict.json (read/write ./, no network, no native modules) and lavamoat/scripts.loose.json (broad file reads, temp-dir writes, child processes and native addons allowed, no network) — auto-generated when script hardening is enabled. Not checked yet Supports a null profile (lavamoat/scripts.null.json with { "NODE_OPTIONS": {} }) to explicitly opt a script out of all permission restrictions. Not checked yet Adds --allow-fs-tmp extension to the Node.js permission model, granting write access to the OS temporary directory without requiring a hardcoded platform-specific path. Not checked yet
+2 more
show less
Applies permission profiles by injecting NODE_OPTIONS at script-launch time via package manager hooks — intercepting the shell for npm and pnpm, and using the wrapScriptExecution hook for yarn — requiring no changes to script code itself. Not checked yet Note: node --run is not currently supported; permission flags will not be applied when scripts are invoked via node --run. Not checked yet
7 details in Everything
@lavamoat/harden CLI applies opinionated security hardening to npm/yarn/pnpm project configs via three commands: defaults, wizard, and check.
└──▷ TRY IT
Run in CI to verify a project meets moderate hardening without changing any files — fails the build if gaps exist.
copy
$ harden check --level moderate
Capture a team's agreed hardening decisions once, then replay them deterministically in CI or onboarding without re-running the interactive wizard.
copy
$ harden wizard -s
harden defaults -d ./decisions-snapshot.json
New harden defaults command writes hardening config at a chosen level (baseline, moderate, strict) into .npmrc, .yarnrc.yml, pnpm-workspace.yaml, and package.json; accepts --level (-l) and --package-manager (-p) flags. Not checked yet New harden check command audits the current package manager config against a hardening level without modifying files, printing a pass/fail checklist and exiting with code 0 (all satisfied) or 1 (gaps found) — designed for CI enforcement. Not checked yet New harden wizard command interactively walks through hardening decisions and applies only the settings the user selects, with optional --package-manager (-p) pre-selection. Not checked yet New --decisions-snapshot (-d) flag loads a JSON file of saved hardening decisions to pre-fill the wizard or override level-based defaults in defaults; --save-decisions (-s) writes the result to ./decisions-snapshot.json for reuse. Not checked yet Adds a lavamoat/.env.ban.json file to censor environment variables by name pattern during package.json script execution. Not checked yet
+4 more
show less
Adds a scriptsConfig field to package.json to assign per-script Node.js Permissions option files, with a #default fallback, hardening the script execution environment. Not checked yet Supports npm v11.18+, Yarn v4.16+, and pnpm v11+ as target package managers, enforcing minimum versions that unlock security-relevant features such as --ignore-scripts support and git dependency limits. Not checked yet Integrates @lavamoat/allow-scripts for precise per-package, version-pinned lifecycle script allowlisting under yarn (requires node_modules layout instead of Plug'n'Play). Not checked yet Includes pnpm's trustPolicy: no-downgrade and package-manager-specific age gates and git dependency limitations at the baseline level and above. Not checked yet
9 details in Everything
@lavamoat/harden CLI applies opinionated security hardening to npm/yarn/pnpm configs via harden defaults, harden wizard, and harden check commands.
└──▷ TRY IT
Enforce a strict hardening baseline in CI — fails the build if any strict-level opinions are not satisfied.
copy
$ harden check --level strict
Capture wizard decisions once and replay them non-interactively across all developer machines or pipelines.
copy
$ harden wizard -s
harden defaults -d ./decisions-snapshot.json
Apply baseline hardening explicitly to a yarn project without relying on package manager auto-detection.
copy
$ harden defaults -p yarn --level baseline
Adds harden defaults --level <level> command to write hardening config into .npmrc, .yarnrc.yml, pnpm-workspace.yaml, and package.json at baseline, moderate, or strict levels without manual edits. Not checked yet Adds --package-manager (-p) flag to harden defaults and harden check to explicitly target npm, yarn, or pnpm instead of relying on auto-detection. Not checked yet Adds --decisions-snapshot (-d) flag to load a JSON file of saved hardening decisions, and --save-decisions (-s) to write the final choices to ./decisions-snapshot.json for reuse across teams or CI. Not checked yet Adds harden check --level <level> command that audits the current package manager config against a hardening level and exits with code 0 (all satisfied) or 1 (gaps found) — suitable for CI enforcement. Not checked yet Adds harden wizard interactive command that assesses the project and lets practitioners selectively apply hardening settings by answering prompts, with optional decisions snapshot pre-fill via -d. Not checked yet
+4 more
show less
Introduces a lavamoat/.env.ban.json file for censoring environment variables by name pattern during package.json script execution. Not checked yet Adds a scriptsConfig field in package.json for selecting per-script Node.js Permissions option files, with a #default fallback, to restrict runtime access during script execution. Not checked yet Enforces minimum package manager versions (npm v11.18+, Yarn v4.16+, pnpm v11+) to guarantee availability of security-relevant features such as --ignore-scripts support and git dependency limits. Not checked yet Rearranges $PATH during script execution to mitigate bin confusion attacks. Not checked yet
9 details in Everything
allow-scripts gains a check command to detect stale allow-lists in CI pipelines.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v5.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v5.1.0
└──▷ TRY IT
Run in CI to fail fast if the allow-scripts config no longer matches installed packages.
copy
$ npx allow-scripts check
New check command warns when the allow-scripts configuration is out of date, enabling CI to catch unapproved lifecycle script changes before they reach production. Not checked yet
1 detail in Everything
allow-scripts-v5.1.0
Jun 25, 2026
·
issue 014
allow-scripts gains a check command to detect stale allow-lists in CI without making changes.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v5.1.0 https://github.com/LavaMoat/LavaMoat.git
$ git checkout allow-scripts-v5.1.0
└──▷ TRY IT
Catch unapproved or newly-added install scripts in CI before they can run — fails with a warning instead of silently passing.
copy
$ npx @lavamoat/allow-scripts check
Adds a check command that warns when the allow-scripts configuration is out of date, designed for use in CI pipelines without modifying any files. Not checked yet
1 detail in Everything
LavaMoat webpack plugin gains sourcemap-preserving evasive transforms for easier debugging of hardened bundles.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v2.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v2.2.0
Adds sourcemap-preserving evasive transforms, keeping source maps intact after LavaMoat's security-oriented code transformations. Not checked yet
1 detail in Everything
lavamoat-node gains opt-in modernized module resolution for classic mode
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-v11.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-v11.1.0
Laverna v2.1.0 adds Yarn support for automated LavaMoat policy publishing.
└──▷ GET THIS VERSION
copy
$ git clone --branch laverna-v2.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout laverna-v2.1.0
Supports Yarn as a package manager alongside the existing npm support. Not checked yet
1 detail in Everything
allow-scripts v5 pins install scripts to exact versions by default, tightening supply-chain control.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v5.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v5.0.0
Install scripts are now pinned to specific package versions, preventing allowlisted scripts from running under unintended versions. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! allow-scripts no longer matches a lower version against an allowed entry — version pinning is now exact, so existing allowlist entries that relied on lower-version matching will stop working.! allow-scripts defaults to pinning versions; upgrading requires a migration action to update existing allowlist configuration.
LavaMoat webpack plugin now auto-overrides unsafe devtool settings that break LavaMoat's security guarantees.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v2.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v2.1.0
Automatically overrides the webpack devtool setting when it is likely to break LavaMoat, preventing silent security misconfigurations. Not checked yet
1 detail in Everything
LavaMoat types v1.0.0 adds include property to the LavaMoatPolicy type.
└──▷ GET THIS VERSION
copy
$ git clone --branch types-v1.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout types-v1.0.0
└──▷ BREAKING ON UPGRADE
! Node.js v18 is no longer supported; upgrading will break installations running on Node.js v18.
LavaMoat Node 1.0.0 adds parallel module inspection and major Node.js compatibility updates.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v1.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v1.0.0
Adds parallel module inspection, speeding up policy generation for large dependency trees. Not checked yet Major compatibility changes bringing LavaMoat Node to a stable 1.0 release. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! Node.js v18 is no longer supported; upgrade to Node.js v20 or later before upgrading this package.
lavamoat-core v18 exports the MODULE_REFS constant for programmatic policy inspection.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v18.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v18.0.0
└──▷ USE IT
Import MODULE_REFS to reference canonical module identifier keys when building or inspecting LavaMoat policies programmatically.
javascript
copy
import { MODULE_REFS } from 'lavamoat-core'
// Use MODULE_REFS to look up entries in a generated policy
const ref = MODULE_REFS.some_key
console.log(policy.resources[ref])
└──▷ BREAKING ON UPGRADE
! Node.js v18 is no longer supported; upgrading requires Node.js v20 or later.
LavaMoat Node now returns the top-level export as the return value of runLava
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-v10.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-v10.1.0
lavamoat-tofu 8.1.0 adds deep ES module dependency analysis and informative policy-merge error messages.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-tofu-v8.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-tofu-v8.1.0
Enables deep dependency analysis of ES modules, allowing tofu to traverse transitive ES module imports when generating policies. Not checked yet Adds informative errors when a policy merge produces invalid entries, surfacing actionable diagnostics instead of silent failures. Not checked yet
2 details in Everything
LavaMoat Core 17.1.0 adds informative errors when policy merge produces invalid entries.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v17.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v17.1.0
LavaMoat webpack plugin adds a meta field to policy resources to surface webpack optimization info.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v1.5.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v1.5.0
Adds a meta field to policy resource entries, recording webpack optimization data (e.g. sideEffect tree-shaking) for each module. Not checked yet
1 detail in Everything
LavaMoat types v0.1.0 adds a meta field to policy resources for surfacing webpack optimization reports.
└──▷ GET THIS VERSION
copy
$ git clone --branch types-v0.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout types-v0.1.0
Adds a meta field to the policy resource type, enabling webpack optimization data to be reported alongside policy entries. Not checked yet
1 detail in Everything
LavaMoat webpack plugin officially releases scuttling support and adds tree-shake-safe policy enforcement.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v1.4.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v1.4.0
└──▷ USE IT
Enable scuttling in your webpack build to lock down global object access at runtime, preventing supply-chain attacks from abusing globals.
javascript
copy
// webpack.config.js
const { LavaMoatPlugin } = require('@lavamoat/webpack');
module.exports = {
plugins: [
new LavaMoatPlugin({
scuttling: true,
}),
],
};
Officially releases and documents the scuttling feature in the webpack plugin, enabling runtime lockdown of global object access for bundled code. Not checked yet
1 detail in Everything
LavaMoat webpack plugin now officially supports scuttling with documentation.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.7.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.7.0
allow-scripts now recommends global installation for simpler, project-wide lifecycle script control.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v3.4.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v3.4.0
Supports global installation of allow-scripts as the recommended usage pattern, enabling consistent lifecycle script enforcement across projects without per-project setup. Not checked yet
1 detail in Everything
LavaMoat webpack plugin v1.3.0 adds generatePolicyOnly mode, null runtime support, and per-chunk runtime configuration.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v1.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v1.3.0
└──▷ USE IT
Generate a LavaMoat policy file during CI without applying sandbox protections — lets you audit or commit the policy separately from the production build.
javascript
copy
// webpack.config.js
const { LavaMoatPlugin } = require('@lavamoat/webpack');
module.exports = {
plugins: [
new LavaMoatPlugin({
generatePolicyOnly: true,
}),
],
};
Embed different LavaMoat runtime options per chunk — useful when entry points have different trust boundaries or performance requirements.
javascript
copy
// webpack.config.js
const { LavaMoatPlugin } = require('@lavamoat/webpack');
module.exports = {
plugins: [
new LavaMoatPlugin({
runtimeConfigurationPerChunk_experimental: {
main: { trustRoot: true },
vendor: { trustRoot: false },
},
}),
],
};
Adds generatePolicyOnly option to run the plugin in policy-generation mode without applying protections, useful for CI policy auditing without a full build. Not checked yet Adds null runtime support, enabling LavaMoat to work in webpack configurations that use no runtime chunk. Not checked yet Adds runtimeConfigurationPerChunk_experimental option to embed and control LavaMoat runtime options on a per-chunk basis. Not checked yet Adds static shims for the webpack runtime, reducing reliance on dynamic runtime injection. Not checked yet Emits explicit error messages when a webpack compilation completes with no modules protected, surfacing misconfiguration early. Not checked yet
5 details in Everything
LavaMoat Core 16.6.0 adds Firefox content-script support for cross-realm window prototypes.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.6.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.6.0
LavaMoat webpack plugin gains improved handling for globals requiring more than a simple unwrap from core.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v1.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v1.2.0
Adds support for globals that require more complex handling beyond a simple unwrap from lavamoat-core, improving compatibility with a wider range of webpack bundles. Not checked yet
1 detail in Everything
LavaMoat node v0.4.0 improves git-safe resilience against network and git instability.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v0.4.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v0.4.0
Increases resilience of git-safe against adverse network conditions and git edge cases. Not checked yet
1 detail in Everything
git-safe-dependencies v0.3.0 increases resilience against network conditions and git issues.
└──▷ GET THIS VERSION
copy
$ git clone --branch git-safe-dependencies-v0.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout git-safe-dependencies-v0.3.0
Improves resilience against network conditions and git failures when verifying safe dependencies. Not checked yet
1 detail in Everything
react-native-lockdown bumps to SES 1.14.0 for hardened JavaScript in React Native apps.
└──▷ GET THIS VERSION
copy
$ git clone --branch react-native-lockdown-v0.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout react-native-lockdown-v0.1.0
Upgrades bundled SES (Hardened JavaScript) runtime to v1.14.0, bringing its latest compartment isolation and intrinsic hardening to React Native. Not checked yet
1 detail in Everything
LavaMoat webpack plugin v1.1.0 shields the webpack runtime from scuttling and ships proper TypeScript types.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v1.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v1.1.0
Defends the webpack runtime from scuttling, preventing untrusted code from corrupting webpack's own globals at runtime. Not checked yet Exposes proper TypeScript types for the LavaMoat webpack plugin, enabling typed configuration in TS projects. Not checked yet
2 details in Everything
LavaMoat webpack plugin hits v1.0.0 with scuttling, lazy-chunk protection, context-module support, and hardened defaults.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v1.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v1.0.0
└──▷ USE IT
Harden a webpack bundle by enabling scuttling to prevent dependency packages from accessing or mutating privileged globals.
javascript
copy
// webpack.config.js
const LavaMoatPlugin = require('@lavamoat/webpack');
module.exports = {
plugins: [
new LavaMoatPlugin({
scuttling: true,
}),
],
};
Opt a legacy or third-party chunk out of LavaMoat protection while the rest of the bundle stays hardened.
javascript
copy
// webpack.config.js
const LavaMoatPlugin = require('@lavamoat/webpack');
module.exports = {
plugins: [
new LavaMoatPlugin({
unlockedChunksUnsafe: ['legacy-vendor'],
}),
],
};
Experiment with dynamic require / context modules under LavaMoat without leaving them fully unguarded.
javascript
copy
// webpack.config.js
const LavaMoatPlugin = require('@lavamoat/webpack');
module.exports = {
plugins: [
new LavaMoatPlugin({
__unsafeAllowContextModules: true,
}),
],
};
Adds scuttling support (scuttling option) to lock down global object properties in webpack bundles at runtime. Not checked yet New unlockedChunksUnsafe option lets teams selectively opt specific chunks out of LavaMoat protection for incremental adoption. Not checked yet Supports webpack context modules and chunk lazy-loading, enabling policy enforcement on dynamically imported code. Not checked yet Adds experimental __unsafeAllowContextModules flag to test context-module scenarios without leaving them fully unprotected. Not checked yet Enables syntax checks by default, running validation before module concatenation to catch policy-breaking code earlier. Not checked yet
+2 more
show less
Suppresses resource asset emission from packages by default, reducing unintended file exposure in build output. Not checked yet New policy debugging capabilities for inspecting and testing generated LavaMoat policies. Not checked yet
7 details in Everything
└──▷ BREAKING ON UPGRADE
! Deprecated lockdown options have been removed from @lavamoat/webpack and lavamoat-core; configurations using those options will break on upgrade.
New @lavamoat/react-native-lockdown beta brings SES-based runtime hardening to React Native apps.
└──▷ GET THIS VERSION
copy
$ git clone --branch react-native-lockdown-v0.0.1 https://github.com/lavamoat/lavamoat.git
$ git checkout react-native-lockdown-v0.0.1
Introduces @lavamoat/react-native-lockdown, a new LavaMoat library that applies SES (Secure ECMAScript) lockdown to React Native environments. Not checked yet Ships with a vendored SES build, making the lockdown self-contained without relying on an external SES package. Not checked yet
2 details in Everything
LavaMoat Node v0.3.0 adds scuttling support and custom errors for tighter runtime sandbox control.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v0.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v0.3.0
Adds scuttling support, enabling LavaMoat to restrict access to powerful globals on the Node.js runtime environment. Not checked yet Adds custom error types for more precise programmatic handling of LavaMoat policy and sandbox violations. Not checked yet
2 details in Everything
LavaMoat core adds Node.js scuttling support and relaxes scuttling to skip intrinsics, reducing false-positive lockdowns.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.5.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.5.0
Adds scuttling support for Node.js environments, extending runtime prototype-pollution defenses to Node targets. Not checked yet Relaxes scuttling by skipping JavaScript intrinsics, reducing breakage when hardening globals without affecting built-in objects. Not checked yet
2 details in Everything
LavaMoat Node v0.2.0 adds support for running untrusted entrypoints under policy enforcement.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v0.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v0.2.0
Supports untrusted entrypoints, allowing policy enforcement to apply even when the application entry script itself is not fully trusted. Not checked yet
1 detail in Everything
LavaMoat Core 16.4.0 adds a redefine global policy value and support for untrusted entrypoints.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.4.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.4.0
└──▷ USE IT
Grant a package the ability to redefine a global (e.g. fetch) rather than merely reading it, using the new "redefine" policy value.
json
copy
{
"resources": {
"some-package": {
"globals": {
"fetch": "redefine"
}
}
}
}
Adds "redefine" as a new global policy value in the LavaMoat policy schema, giving policy authors finer-grained control over how globals are exposed to packages. Not checked yet Supports untrusted entrypoints, allowing LavaMoat to apply compartment isolation even when the application entry module itself is not fully trusted. Not checked yet
2 details in Everything
LavaMoat webpack plugin now supports webpack context modules and chunk lazy loading.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.10.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.10.0-beta.0
LavaMoat Node v0.1.0 adds --quiet/--verbose output control and improved entrypoint UX
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v0.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v0.1.0
Adds --quiet and --verbose flags for controlling output verbosity when running LavaMoat Node. Not checked yet Improves UX for specifying entrypoints, making it easier to define application entry in LavaMoat Node. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! dev mode is now disabled by default; setups that relied on dev mode being on by default will no longer behave the same after upgrading.
LavaMoat webpack plugin v0.9.0-beta.0 adds scuttling support to harden global object access in bundled apps.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.9.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.9.0-beta.0
Adds scuttling support to the webpack plugin, restricting untrusted modules from accessing or tampering with privileged globals at runtime. Not checked yet
1 detail in Everything
LavaMoat v0.0.2 now allows passing arbitrary flags to the Node.js entrypoint.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v0.0.2 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v0.0.2
LavaMoat git-safe-dependencies adds a GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. workflow validator to catch unsafe action dependencies.
└──▷ GET THIS VERSION
copy
$ git clone --branch git-safe-dependencies-v0.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout git-safe-dependencies-v0.2.0
LavaMoat introduces @lavamoat/node, a new Node.js runtime protection library.
└──▷ GET THIS VERSION
copy
$ git clone --branch node-v0.0.1 https://github.com/lavamoat/lavamoat.git
$ git checkout node-v0.0.1
Introduces @lavamoat/node, a new LavaMoat package for applying supply-chain security policies in Node.js environments. Not checked yet
1 detail in Everything
LavaMoat Core 16.3.0 adds policy debugging capabilities to the webpack integration.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.3.0
LavaMoat webpack plugin gains policy debugging, safer context-module experiments, and tighter resource-asset controls.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.8.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.8.0-beta.0
└──▷ USE IT
Opt in to context-module support during development without leaving them fully unrestricted — useful when testing dynamic require() patterns.
javascript
copy
new LavaMoatPlugin({
__unsafeAllowContextModules: true
})
Adds __unsafeAllowContextModules flag to safely experiment with webpack context modules without leaving them exposed by default. Not checked yet Suppresses emission of resource assets from packages by default, reducing unintended asset exposure. Not checked yet Adds policy debugging capabilities for inspecting and troubleshooting LavaMoat policy resolution in webpack builds. Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! Resource assets from packages are no longer emitted by default; builds that relied on automatic resource asset emission will need to explicitly enable it.
LavaMoat ships git-safe-dependencies v0.1.0, a new tool for securing git-sourced Node.js dependencies.
└──▷ GET THIS VERSION
copy
$ git clone --branch git-safe-dependencies-v0.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout git-safe-dependencies-v0.1.0
lavamoat-browserify 18.1.0 lets you override the module resolve implementation for custom dependency resolution.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-browserify-v18.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-browserify-v18.1.0
Supports overriding the resolve implementation, enabling custom module resolution logic in browserify builds. Not checked yet
1 detail in Everything
LavaMoat Core 16.2.0 adds diff-friendly policy sorting and makes mergePolicy's second param explicitly optional.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.2.0
└──▷ USE IT
Merge a single policy without a second argument now that the param is explicitly optional.
javascript
copy
import { mergePolicy } from 'lavamoat-core'
const merged = mergePolicy(existingPolicy)
Sorts LavaMoat policy files in a diff-friendly way so sort order remains stable even when a dependency's path changes, reducing noisy diffs on policy updates. Not checked yet Adds a policy sorting CLI helper to migrate existing policy files to the new cleaner sort order. Not checked yet Makes the second parameter of mergePolicy explicitly optional, simplifying single-policy merge calls. Not checked yet
3 details in Everything
lavamoat-core now exports endowmentsToolkit from the package root for easier direct access.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.1.0
└──▷ USE IT
Access endowmentsToolkit directly from the package root instead of hunting for an internal module path.
javascript
copy
import { endowmentsToolkit } from 'lavamoat-core'
Exports endowmentsToolkit directly from the lavamoat-core root, removing the need to import from a deep internal path. Not checked yet
1 detail in Everything
LavaMoat webpack plugin gains reconfigured lockdown inlining and thisAsExports runtime support.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.7.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.7.0-beta.0
Changes how inlining of SES lockdown is configured in the webpack plugin. Not checked yet Adds support for the thisAsExports webpack runtime requirement, broadening compatibility with CommonJS modules that rely on this as their exports object. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! The way inlining lockdown is configured has changed — existing plugin configuration for lockdown inlining will need to be updated to match the new interface.
allow-scripts v3.3.0 lets you configure which lifecycle events are loaded via loadAllPackageConfigurations.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v3.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v3.3.0
Supports configuring lifecycleEvents when calling loadAllPackageConfigurations, giving programmatic control over which npm lifecycle hooks are evaluated. Not checked yet
1 detail in Everything
LavaMoat webpack plugin adds ContextModule support and improved HMR compatibility in v0.6.0-beta.0
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.6.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.6.0-beta.0
Supports webpack ContextModule by skipping policy enforcement for dynamic require contexts, enabling broader webpack project compatibility. Not checked yet Handles HMR-instrumented code gracefully even when Hot Module Replacement is not enabled, preventing build errors in non-HMR setups. Not checked yet
2 details in Everything
lavamoat-core v16 adds a global store with attenuation support and consistent negative policy override handling for builtins.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v16.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v16.0.0
Adds a global store with attenuation support, enabling attenuated access to global references across LavaMoat compartments. Not checked yet Makes makeMinimalViewOfRef usage in builtin attenuation consistent with globals for negative policy overrides, now implemented in endowmentsToolkit for reuse by the webpack plugin. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! Node.js v16 is no longer supported by lavamoat-core (and lavamoat-browserify, lavamoat-node, lavamoat-perf, lavamoat-tofu, lavamoat-webpack).
LavaMoat v18 drops Node.js v16 support and adds compatibility for Node.js ^22.5.1 across all packages.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-browserify-v18.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-browserify-v18.0.0
Adds support for Node.js ^22.5.1 in the node, browserify, and perf components Not checked yet Removes support for Node.js v16 from all workspace packages (core, node, browserify, perf, tofu, webpack) Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! The tool no longer runs on Node.js v16; upgrades to v18.0.0 will fail or crash on that version.
allow-scripts v3.2.0 exports new policy-loading APIs and exposes canonical name maps for programmatic use.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v3.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v3.2.0
└──▷ USE IT
Audit CI for any packages missing an allow-scripts policy entry without running the CLI directly.
javascript
copy
const { loadAllPackageConfigurations, printMissingPoliciesIfAny } = require('@lavamoat/allow-scripts');
const config = await loadAllPackageConfigurations({ rootDir: process.cwd() });
printMissingPoliciesIfAny(config);
Resolve canonical package names from filesystem paths when building custom policy tooling.
javascript
copy
const { loadAllPackageContents } = require('@lavamoat/allow-scripts');
const contents = await loadAllPackageContents({ rootDir: process.cwd() });
console.log(contents.canonicalNamesByPath); // { '/path/to/node_modules/lodash': 'lodash', ... }
Exports loadAllPackageConfigurations and printMissingPoliciesIfAny for programmatic access to package script policies. Not checked yet Exposes canonicalNamesByPath on the result of loadAllPackageContents for mapping install paths to canonical package names. Not checked yet
2 details in Everything
LavaMoat webpack plugin gains builtin attenuation by policy and a global store with attenuation support.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.5.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.5.0-beta.0
Adds a global store with attenuation support, enabling fine-grained control over shared global state across packages. Not checked yet Adds built-in module support in the webpack plugin options and build-time policy generation. Not checked yet Adds built-in module support in the webpack runtime, allowing builtins to be tracked and controlled at runtime. Not checked yet Enables attenuation of Node.js built-in modules via LavaMoat policy in webpack bundles. Not checked yet Supports Node.js ^22.5.1 for the webpack plugin. Not checked yet
5 details in Everything
└──▷ BREAKING ON UPGRADE
! Node.js v16 is no longer supported by lavamoat-webpack (or lavamoat-core, lavamoat-browserify, lavamoat-node, lavamoat-perf, or lavamoat-tofu); upgrading requires Node.js v18 or later.
Lavamoat Tofu v7.3.0 adds support for Node.js 22.x
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-tofu-v7.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-tofu-v7.3.0
lavamoat-tofu-v7.3.0 extends compatibility to include Node.js 22.x Not checked yet
1 detail in Everything
LavaMoat v2.1.0 adds allow-scripts support for Node.js v22
└──▷ GET THIS VERSION
copy
$ git clone --branch preinstall-always-fail-v2.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout preinstall-always-fail-v2.1.0
LavaMoat v1.2.0 adds support for Node.js v22 in the allow-scripts feature
└──▷ GET THIS VERSION
copy
$ git clone --branch laverna-v1.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout laverna-v1.2.0
Lavamoat v15.4.0 adds Node.js 22 support
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v15.4.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v15.4.0
Adds nodejs 22 runtime support to lavamoat-core Not checked yet
1 detail in Everything
LavaMoat webpack plugin adds lockdown inlining feature
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.4.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.4.0-beta.0
allow-scripts-v3.1.0 now supports Node.js v22.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v3.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v3.1.0
Supports Node.js v22 in allow-scripts. Not checked yet
1 detail in Everything
LavaMoat v4.3.0 adds support for Node.js v22
└──▷ GET THIS VERSION
copy
$ git clone --branch aa-v4.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout aa-v4.3.0
allow-scripts now supports Node.js v22 Not checked yet
1 detail in Everything
LavaMoat 1.1.0 adds automatic CI support
└──▷ GET THIS VERSION
copy
$ git clone --branch laverna-v1.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout laverna-v1.1.0
Adds automatic CI detection and configuration handling to the laverna subsystem Not checked yet
1 detail in Everything
lavamoat-core v15.3.0 adds external package name fallback function in generatePolicy
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v15.3.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v15.3.0
Adds externalPackageNameFallback option to generatePolicy to control how external package names are resolved when webpack's default method fails. Not checked yet
1 detail in Everything
LavaMoat webpack now generates external package name fallbacks in policies via generatePolicy
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.3.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.3.0-beta.0
└──▷ USE IT
Configure LavaMoat to fall back to a specific name when an external package name cannot be resolved, ensuring valid policy generation.
code
copy
const policy = generatePolicy(webpackConfig, { externalPackageNamesFallback: 'fallback-package-name' });
Adds generatePolicy function with externalPackageNamesFallback option to use fallback names for external packages in the generated webpack policy Not checked yet
1 detail in Everything
Adds unknown package directory logging in LavaMoat aa build process
└──▷ GET THIS VERSION
copy
$ git clone --branch aa-v4.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout aa-v4.2.0
Logs unknown package directories in the error message when running lava-mocha-strict or similar aa tooling Not checked yet
1 detail in Everything
LavaMoat v15.2.0 adds ESM policy support, improved error paths, and default ses lockdown changes
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v15.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v15.2.0
└──▷ USE IT
Generate a security policy for an ESM-based project that previously failed or produced incomplete coverage.
shell
copy
lavamoat generate --esm
Adds ESM support in policy generation allowing Lavamoat to create policies for ECMAScript modules Not checked yet Changes the default value of localeTaming in ses lockdown to be turned off Not checked yet Improves error reporting by returning the attempted path when JSON policy parsing fails Not checked yet
3 details in Everything
LavaMoat webpack plugin adds policy generation/loading/overrides and support for __webpack_require__.g.
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.2.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.2.0-beta.0
Adds experimental policy generation, loading, and override support to the webpack integration. Not checked yet Supports webpack's use of __webpack_require__.g as the global object in lockdown contexts. Not checked yet
2 details in Everything
Adds custom resolver support and symlink compatibility for LavaMoat aa
└──▷ GET THIS VERSION
copy
$ git clone --branch aa-v4.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout aa-v4.1.0
aa now supports a customResolver option for resolving packages during installation Not checked yet
1 detail in Everything
lavapack-v6.1.0 adds independent module syntax checking to lavapack
└──▷ GET THIS VERSION
copy
$ git clone --branch lavapack-v6.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavapack-v6.1.0
lavapack now checks the syntax of a module independently of browserify's own check Not checked yet
1 detail in Everything
lavamoat-tofu v7.2.0 adds ESM support for cyber tooling integration
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-tofu-v7.2.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-tofu-v7.2.0
Add ESM support Not checked yet
1 detail in Everything
LavaMoat tofu v7.1.0 introduces TypeScript type definitions for improved development experience.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-tofu-v7.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-tofu-v7.1.0
Provides TypeScript type definitions for the tofu module to enable static analysis and IDE support Not checked yet
1 detail in Everything
lavamoat-core-v15.1.0 ships TypeScript types
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v15.1.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v15.1.0
lavamoat-core now ships with TypeScript type definitions. Not checked yet
1 detail in Everything
LavaMoat webpack plugin now emits lockdown.js to dist in v0.1.0-beta.0
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.1.0-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.1.0-beta.0
webpack-v0.1.0-beta.0 adds emitting lockdown.js to the build dist directory, enabling self-contained LavaMoat execution without external runtime injection. Not checked yet
1 detail in Everything
lavamoat-viz v7 adds Node.js 20 support
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-viz-v7.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-viz-v7.0.0
node20: Adds support for Node.js 20 Not checked yet The minimum supported Node.js version is now v16.20.0 Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! Drop support for Node.js v14; the minimum supported version is now v16.20.0
LavaMoat v8 adds overrideTaming: severe and Node.js 20 support.
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-v8.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-v8.0.0
Adds overrideTaming: 'severe' to improve developer experience for policy overrides Not checked yet Drops Node.js v14 support and sets minimum supported version to v16.20.0 Not checked yet Adds Node.js 20 (v20) runtime support Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! The minimum supported Node.js version is now v16.20.0, dropping support for Node.js v14
LavaMoat v6 adds Node.js 20 support and raises minimum supported version to 16.20.0
└──▷ GET THIS VERSION
copy
$ git clone --branch lavapack-v6.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavapack-v6.0.0
└──▷ USE IT
Ensure your project uses the LavaMoat pack compatible with modern Node.js runtimes
shell
copy
npm install --save-dev lavamoat@lavapack-v6
Adds lavapack-v6 release with native Node.js 20 support via the new node20 package Not checked yet Raises the minimum supported Node.js runtime version to v16.20.0, dropping legacy Node.js v14 compatibility Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! The minimum supported Node.js version is now v16.20.0; running on Node.js v14 or lower will fail.
lavamoat-core v15.0.0 adds overrideTaming: 'severe' and Node.js 20 support
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-core-v15.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-core-v15.0.0
Adds overrideTaming: 'severe' to lavamoat config for improved developer experience Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The minimum supported Node.js version is now v16.20.0
LavaMoat v17 adds overrideTaming and Node.js 20 support; raises minimum Node to v16.20.0
└──▷ GET THIS VERSION
copy
$ git clone --branch lavamoat-browserify-v17.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout lavamoat-browserify-v17.0.0
Adds overrideTaming config key with severe option for improved developer experience Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The minimum supported Node.js version is now v16.20.0; installations on older versions will fail.
Initial release of LavaMoat's webpack plugin and scorchwrap with default lockdown options
└──▷ GET THIS VERSION
copy
$ git clone --branch webpack-v0.0.1-beta.0 https://github.com/lavamoat/lavamoat.git
$ git checkout webpack-v0.0.1-beta.0
LavaMoat allow-scripts 3.0 now ships TypeScript declarations for improved type safety.
└──▷ GET THIS VERSION
copy
$ git clone --branch allow-scripts-v3.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout allow-scripts-v3.0.0
└──▷ BREAKING ON UPGRADE
! The minimum supported Node.js version is now v16.20.0.
LavaMoat v4.0.0 ships generated TypeScript types for programmatic use
└──▷ GET THIS VERSION
copy
$ git clone --branch aa-v4.0.0 https://github.com/lavamoat/lavamoat.git
$ git checkout aa-v4.0.0
Adds aa-scoped generated TypeScript type definitions to the package Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The minimum supported Node.js version is now v16.20.0.