Re-enable flow scanner

[RubenHalman]

The lightning-flow-scanner (sfdx) package, used for scanning Salesforce Lightning Flows, has been deprecated and unpublished from the npm registry due to a vulnerability in its core dependency, lightning-flow-scanner-core. The vulnerability, caused by unsafe custom rule loading, has been addressed in the v5 release of the core.

I have prepared a PR which changes the documentation to fix broken links:
[https://github.com//pull/6359)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[RubenHalman]

After years of Megalinter and SFDX Hardis relying on Lightning Flow Scanner, it would be good to get some clarity on the status and next steps here.

[nvuillam]

@RubenHalman let's discuss it someday
MegaLinter can't afford to have lfs sudfenly retired again so we have to make sure it won't happen

[RubenHalman]

@nvuillam Auto-closing via bots as "completed" while saying "let's discuss it someday" seems contradictory.
If you want to talk about the future of LFS and avoid sudden breaks for MegaLinter/sfdx-hardis users, lets at least keep the issue open so others can follow/contribute.

[nvuillam]

@RubenHalman i agree but i don't understand, as you closed the issue yourself :/

I reopened the issue

[RubenHalman]

@nvuillam Thank you. Perhaps I did something wrong, but nothing I tried removed the O: stale status, so that's why I went ahead and closed the ticket, hoping it can either be re-opened or a new one created if needed.