@flow-scanner/lightning-flow-scanner-core 6.2.1 → 6.3.0

package/CONTRIBUTING.md

@@ -6,18 +6,19 @@ Since 2021, the _Lightning Flow Scanner_ has grown from its roots as VS Code too
 - 📢 Sharing our work with your network
 - 💬 Sharing feedback to help us improve
 - 💻 Contributing code to drive innovation
+- 🤝 [Become a member](https://register.lightningflowscanner.org/) to stay connected.
 
 ### I have a Question/Feedback
 
 For general questions, ideas, or seeking input on topics that might (or might not) turn into issues, we recommend to use our [Discussions](https://github.com/orgs/Flow-Scanner/discussions) forum. This is best for open-ended conversations, brainstorming, and gathering community input before creating a feature request.
 
-If it's more specific like a bug or a new feature—use [GitHub Issues](https://github.com/features/issues) instead. Before creating a new issue, please take a moment to search the existing [Issues](/issues) to prevent duplicates. If you find something relevant, adding an upvote helps us understand demand and prioritize better. We've prepared a few templates to guide you through the process of issue reporting:
+If it's more specific like a bug or a new feature—use [GitHub Issues](https://github.com/features/issues) instead. Before creating a new issue, please take a moment to search the existing [Issues](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues) to prevent duplicates. If you find something relevant, adding an upvote helps us understand demand and prioritize better. We've prepared a few templates to guide you through the process of issue reporting:
 
 ###### Core Engine - For issues or requests related to the core functionality of the scanner, use the following links to submit your request:
 
 - [Report Issue](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new?template=bug_report.md): Report a bug or issue.
 - [Rule Request](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new?template=rule-request.md): Submit a request for a new rule.
-- [Features/Other](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new): Suggest a new feature.
+- [Features/Other](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new): Suggest a new feature or enhancement.
 
 ###### Platforms - For issues or requests related to specific platforms, use the appropriate link below:
 

package/SECURITY.md

@@ -3,15 +3,11 @@
 ## Security Practices
 
 - Code is open-source and peer-reviewed by the community.
-- Vulnerabilities can be reported privately via [GitHub security reporting](https://github.com/Flow-Scanner/lightning-flow-scanner-core/security).
+- Vulnerabilities can be reported privately via [GitHub vulnerability reporting](https://github.com/Flow-Scanner/lightning-flow-scanner-core/security).
 - All changes are **scanned with Snyk** and reviewed before merging.
 - Releases are published to npm using **GitHub Actions Trusted Publishing (OIDC)**.
 - Tags (`v*`) trigger automated `npm publish`, providing a full audit trail.
 
-## Reporting a Vulnerability
-
-If you discover a security vulnerability, please report it using [GitHub vulnerability reporting](https://github.com/Flow-Scanner/lightning-flow-scanner-core/security).
-
 ## Data Handling
 
 This tool collects zero user data. No credentials, PII, payment info, health data, or user content is ever stored, transmitted, or shared. All analysis runs 100% client-side with no network calls to external services.

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@flow-scanner/lightning-flow-scanner-core",
-  "description": "A lightweight, purpose-built engine for parsing and analyzing Salesforce Flow metadata in Node.js or browser environments. Scan, validate, and optimize Flow automations for security risks, best practices, governor limits, and performance bottlenecks.",
-  "version": "6.2.1",
+  "description": "A lightweight and purpose-built engine for Flow metadata in Node.js, and browser environments. Assess and enhance Salesforce Flow automations for best practices, security, governor limits, and performance issues.",
+  "version": "6.3.0",
   "main": "index.js",
   "types": "index.d.ts",
   "engines": {
     "node": "^18 || ^20 || ^22 || ^23"
   },
   "scripts": {
-    "clean": "rm -rf out",
+    "clean": "rimraf out",
     "build:js": "swc src --out-dir out --copy-files --strip-leading-paths --config-file .swcrc",
     "build:types": "tsc -p tsconfig.types.json --declaration --emitDeclarationOnly --outDir out",
     "copy:index": "cp out/main/index.js out/index.js || true",
@@ -46,6 +46,7 @@
     "@types/jest": "29.5.14",
     "@types/node": "22.15.30",
     "@types/semantic-release": "20.0.6",
+    "cross-env": "^10.1.0",
     "eslint": "9.30.0",
     "eslint-plugin-de-morgan": "1.3.0",
     "eslint-plugin-github": "6.0.0",
@@ -56,6 +57,7 @@
     "jest": "30.0.3",
     "lint-staged": "^16.1.2",
     "prettier": "3.6.2",
+    "rimraf": "^6.1.0",
     "ts-node": "10.9.2",
     "typescript": "5.8.3",
     "typescript-eslint": "8.35.0",
@@ -63,7 +65,7 @@
     "vite-plugin-node-polyfills": "0.23.0",
     "vitest": "3.2.4"
   },
-  "homepage": "https://flow-scanner.github.io/lightning-flow-scanner-core",
+  "homepage": "https://dev.lightningflowscanner.org",
   "author": {
     "name": "Ruben Halman",
     "url": "https://github.com/RubenHalman"