Scans for unsafe contexts, hardcoded IDs, and other issues to optimize your Flows.
Use our side bar or the Command Palette and type Flow Scanner to see the list of all available commands.
Configure RulesAllows to define rules and expressions as per defined in the core documentation.Scan Flowsallows choosing either a directory or a selection of flows to run the analysis against.Fix Flowswill apply available fixes automatically.Open Documentationcan be used to reference the documentation.
| Key | Description | Default Value |
|---|---|---|
lightningFlowScanner.SpecifyFiles | Specify flow file paths instead of a root directory. | false |
lightningFlowScanner.NamingConvention | Specify a REGEX expression to use as Flow Naming convention. | "[A-Za-z0-9]+_[A-Za-z0-9]+" |
lightningFlowScanner.APIVersion | Specify an expression to validate the API version, i.e. '===50'(use at least 50). | ">50" |
-
Clone the repo:
git clone https://github.com/Flow-Scanner/lightning-flow-scanner-vsx.git
-
Install dependencies:
npm install
-
run dev environment
npm run watch -
build vsix
npm run build
The original lightning-flow-scanner-vsce package was unpublished from the Visual Studio Marketplace after a Remote Code Execution (RCE) vulnerability was identified in its core dependency, lightning-flow-scanner-core. This issue, caused by unsafe custom rule loading, has been fully resolved in the v5.1.0 release of the core library. The lightning-flow-scanner-vsx fork, focusses on security and maintainability.
Want to help improve Lightning Flow Scanner? See our Contributing Guidelines.