{"repo":"Flow-Scanner/lightning-flow-scanner","free":true,"listed":false,"github":"https://github.com/Flow-Scanner/lightning-flow-scanner","clone":"git clone https://github.com/Flow-Scanner/lightning-flow-scanner.git","description":"Lightning Flow Scanner is an open-source Salesforce CLI plugin, VS Code extension, and GitHub Action for analysing and optimising Salesforce Flows. It scans metadata against 20+ community-driven rules — hardcoded IDs, missing fault paths, inefficient DML, recursion risks, and more. Includes auto-fixes, configurable rules, and CI/CD integration","language":"TypeScript","stars":174,"topics":["security","cicd","monitoring-tool","salesforce","salesforce-cli-plugin","static-analysis","flow","github-action","visual-studio-code-extension","code-quality"],"license":"MIT","category":"dev-tools","readme_excerpt":"v6\" Detect unsafe contexts, queries in loops, hardcoded IDs, and more to optimize Salesforce Flows Also available in the Salesforce Inspector Reloaded extension and OrgCheck app --- Table of contents - Default Rules - Problems - Suggestions - Layout - Configuration - Configure Rules - Define Exceptions - Exclude Flows - Scan Options - Installation - Distributions - CICD Templates - Quick Start - Development --- Default Rules 📌 Tip: To link directly to a specific rule, use the full GitHub anchor link format. Example: https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context Want to help improve this project? See our Contributing Guidelines --- Problems These rules detect anti-patterns and unsafe practices in your Flows that could break functionality, compromise security, or cause deployment failures. DML Statement In A Loop Executing DML operations (insert, update, delete) inside a loop is a high-risk anti-pattern that frequently causes governor limit exceptions. All database operations should be collected and executed once, outside the loop. Rule ID: dml-in-loop Class Name: DMLStatementInLoop Severity: 🔴 Error Hardcoded Id Avoid hard-coding record IDs, as they are unique to a specific org and will not work in other environments. Instead, store IDs in variables—such as merge-field URL parameters or a Get Records element—to make the Flow portable, maintainable, and flexible. Rule ID: hardcoded-id Class Name: HardcodedId Severity: 🔴 Error Hardcoded Secret ","default_branch":null,"files":null,"tree":[],"storefront":"/r/Flow-Scanner","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/Flow-Scanner/lightning-flow-scanner/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}