Releases: Flow-Scanner/lightning-flow-scanner-cli
New: Runtime Beta Mode
Runtime Beta Mode (--betamode / -z)
- Introduces
--betamode(-z) – a runtime flag to enable experimental beta rules during scan. - Default: Disabled (opt-out) – ensures stable, production-safe scans.
- CLI override:
--betamodeforces beta rules even if config saysfalse. - Config support:
betamode: truein.flow-scanner.ymlenables by default. - Precedence: CLI flag > config file > default (
false) - Fully backward compatible – configs without
betamodedefault tofalse. - No code changes needed – core scanner automatically includes
getBetaRules()when enabled.
Compliance Hardened
Compliance Hardened
-
--targetusername/-uflag removed
The ability to retrieve latest Flows from an org viasf project retrieve start(usingchild_process.exec()) has been fully eliminated. -
Zero persistent data
All operations now run 100% within the Node.js runtime. Metadata (e.g., timestamps) is held in-memory only and discarded immediately on exit.
This change ensures full compliance with our new Project's Security Policy, making the CLI plugin more optimal for air-gapped, CI/CD, and enterprise environments.
For users:
Scan local metadata only. Use sf project retrieve manually if needed, then run the scanner on your local force-app/ directory.
→ See: SECURITY.md
The MissingFaultPath rule now correctly ignores "Wait for Amount of Time" and "Wait Until Date" nodes
Upgraded to lightning-flow-scanner-core v5.9.0. This release fixes the MissingFaultPath rule to correctly ignore "Wait for Amount of Time" and "Wait Until Date" nodes, checking fault paths only for relevant nodes like "Wait for Conditions". Resolves Issue #272 (contributed by @chazwatkins). See v5.9.0 release notes for full details.
Security Patch
🚨 v5.6 – Security Patch
🔒 Security Fixes
- Enforced Security Guards
evalandFunctionconstructors are restricted.- Dynamic
import()from remote URLs are blocked.
- Removed loading of custom rules entirely in the core module.
🛡 Audit & Dependency Updates
- Updated dependencies and applied
npm audit fixto resolve known vulnerabilities.
v3.29.0
Full Changelog: v3.27.0...v3.29.0
v3.27.0
Full Changelog: v3.26.0...v3.27.0
3.26.0
Full Changelog: v3.25.0...v3.26.0
3.25.0
Full Changelog: v3.24.0...v3.25.0
3.24.0 | Community Release
Full Changelog: v3.23.0...v3.24.0
3.23.0 | Community Release
What's new?
- Minor fixes to pass suppressed element key from advanced rule to rule common
Full Changelog: v3.22.0...v3.23.0