@flow-scanner/lightning-flow-scanner-core 6.10.6 → 6.11.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@flow-scanner/lightning-flow-scanner-core",
3
3
  "description": "A lightweight 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.",
4
- "version": "6.10.6",
4
+ "version": "6.11.1",
5
5
  "main": "index.js",
6
6
  "exports": {
7
7
  ".": {
@@ -22,7 +22,7 @@
22
22
  "dependencies": {
23
23
  "fast-xml-parser": "^5.3.0"
24
24
  },
25
- "homepage": "https://dev.lightningflowscanner.org",
25
+ "homepage": "https://flow-scanner.github.io/lightning-flow-scanner/",
26
26
  "author": {
27
27
  "name": "Ruben Halman",
28
28
  "url": "https://github.com/RubenHalman"
package/CONTRIBUTING.md DELETED
@@ -1,31 +0,0 @@
1
- ## Contributing Guidelines
2
-
3
- Since 20201, the _Lightning Flow Scanner_ has grown from its roots as VS Code tool to empower Salesforce Developers across six free and open-source platforms—from developer tools to native Salesforce App—delivering a unified experience for robust static analysis of Flows. Our dedicated community has shared their expertise to deepen understanding of Flow optimization. Your support can amplify our impact. Here’s how you can contribute:
4
-
5
- - ⭐ Star or follow the project.
6
- - 📢 Share our work with your network.
7
- - 💬 Share feedback to help us improve.
8
- - 💻 Contribute code by submitting pull requests.
9
- - 🤝 [Join as a member](https://register.lightningflowscanner.org/) to connect.
10
-
11
- ### I have a Question/Feedback
12
-
13
- 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.
14
-
15
- 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/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:
16
-
17
- ###### Core Engine - For issues or requests related to the core functionality of the scanner, use the following links to submit your request:
18
-
19
- - [Report Issue](https://github.com/Flow-Scanner/lightning-flow-scanner/issues/new?template=bug_report.md): Report a bug or issue.
20
- - [Rule Request](https://github.com/Flow-Scanner/lightning-flow-scanner/issues/new?template=rule-request.md): Submit a request for a new rule.
21
- - [Features/Other](https://github.com/Flow-Scanner/lightning-flow-scanner/issues/new): Suggest a new feature or enhancement.
22
-
23
- ###### Platforms - For issues or requests related to specific platforms, use the appropriate link below:
24
-
25
- - [CLI Plugin](https://github.com/Flow-Scanner/lightning-flow-scanner/issues)
26
- - [Copado Plugin](https://github.com/Flow-Scanner/lightning-flow-scanner-copado/issues)
27
- - [GitHub Action](https://github.com/Flow-Scanner/lightning-flow-scanner/issues)
28
- - [Salesforce App](https://github.com/Flow-Scanner/lightning-flow-scanner-app/issues)
29
- - [VS Code/Code Builder](https://github.com/Flow-Scanner/lightning-flow-scanner/issues)
30
-
31
- ###### Thank you
package/SECURITY.md DELETED
@@ -1,55 +0,0 @@
1
- # Security Policy for Lightning Flow Scanner
2
-
3
- ## Security Practices
4
-
5
- - All code is open-source and peer-reviewed by the community.
6
- - Vulnerabilities can be reported privately via [GitHub vulnerability reporting](https://github.com/Flow-Scanner/lightning-flow-scanner/security).
7
- - All changes are scanned with [Snyk](https://github.com/snyk/cli) prior to publication.
8
- - Releases to npm are published using **GitHub Actions Trusted Publishing (OIDC)**.
9
- - Tags (`v*`) trigger automated `npm publish`, providing a full audit trail.
10
-
11
- ## Data Handling
12
-
13
- 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.
14
-
15
- We temporarily use metadata (e.g., Flow metadata, timestamps) in-memory only for real-time functionality during your session. This data is never stored, logged, or transmitted and is discarded immediately when the session ends.
16
-
17
- **Note:** You may manually save scan results (e.g., reports, CSV, JSON) to your local filesystem. These files are created at your request and remain under your full control. This tool does not access, upload, or retain them.
18
-
19
- ## Dependencies
20
-
21
- We actively track and maintain an up-to-date inventory of all third-party dependencies to ensure security and compatibility. Our dependencies include:
22
-
23
- ### Core
24
-
25
- | Package | License | Purpose |
26
- | ----------------- | --------------------------------------------------------------------------------- | ---------------------------------------------- |
27
- | `fast-xml-parser` | [MIT](https://github.com/NaturalIntelligence/fast-xml-parser/blob/master/LICENSE) | Validate XML, Parse XML and Build XML rapidly. |
28
-
29
- ### CLI
30
-
31
- | Package | License | Purpose |
32
- | ----------------------------------- | ------- | ------- |
33
- | `@oclif/core` | [MIT](https://github.com/oclif/oclif/blob/main/LICENSE) | CLI framework core utilities |
34
- | `@salesforce/core` | [BSD-3-Clause](https://github.com/forcedotcom/sfdx-core/blob/main/LICENSE.txt) | Salesforce core library for CLI plugins |
35
- | `@salesforce/sf-plugins-core` | [Apache License 2.0](https://github.com/salesforcecli/sf-plugins-core/blob/main/LICENSE.txt) | Base library for Salesforce CLI plugins |
36
- | `chalk` | [MIT](https://github.com/chalk/chalk/blob/main/license) | Terminal string styling (colors) |
37
- | `cosmiconfig` | [MIT](https://github.com/cosmiconfig/cosmiconfig/blob/main/LICENSE) | Config file loader for JavaScript/Node |
38
- | `glob` | [MIT](https://github.com/isaacs/node-glob/blob/main/LICENSE.md) | File pattern matching |
39
-
40
- ### VSX
41
-
42
- | Package | License | Purpose` |
43
- | ------------------------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------- |
44
- | `cosmiconfig` | [MIT](https://github.com/cosmiconfig/cosmiconfig/blob/main/LICENSE) | Config file loader for JavaScript/Node |
45
- | `glob` | [MIT](https://github.com/isaacs/node-glob/blob/main/LICENSE.md) | File pattern matching |
46
- | `tabulator-tables` | [MIT](https://github.com/olifolkerd/tabulator/blob/master/LICENSE) | Interactive tables and data grids for web apps |
47
- | `uuid` | [MIT](https://github.com/uuidjs/uuid/blob/main/LICENSE.md) | Generates RFC-compliant UUIDs |
48
-
49
- ### Action
50
-
51
- | Package | License | Purpose |
52
- | ------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------- |
53
- | `@actions/core` | [MIT](https://github.com/actions/toolkit/blob/main/packages/github/LICENSE) | Toolkit for developing GitHub Actions |
54
- | `@actions/github` | [MIT](https://github.com/actions/toolkit/blob/main/packages/github/LICENSE) | Interact with the GitHub API in Actions |
55
- | `cosmiconfig` | [MIT](https://github.com/cosmiconfig/cosmiconfig/blob/main/LICENSE) | Config file loader for JavaScript/Node |
Binary file