Pale Moon 27.9.1 suddenly disables NoScript Classic 5.1.8.5

[LigH1L]

From now on, NoScript Classic 5.1.8.5 is classified as an add-on causing security risks (sic!) or instability.

And now?

I was able to reactivate it. And I will probably keep using it as long as I am able.

The "compatible plugins for Pale Moon" page still recommends version 5.0.6.

Is there already any contact to its developers about the reasons why it is now classified as risky? Or is this possibly even a false alarm?
_

Oops, wrong forum, please move to Browser extensions...

[Fedor2]

viewtopic.php?f=46&t=17619 details see there

extensions.blocklist.enabled;false to reactivate

[New Tobin Paradigm]

Fucking hell.. Do not listen to him. Do not disable the bloody blocklist. You can simply re-enable the extension if it gets disabled. However, by default a Level 1 item on the blocklist will not disable an extension. Only warn about it in the Add-ons Manager.

[Moonchild]

Fedor: For the last time: DO NOT recommend that people disable the blocklist, especially not if it's just a warning. The blocklist, when hard-disabled ALSO disables protection against bad drivers being used and known bad plugins. You're suggesting a sledgehammer when a click of a button suffices. Sending people into the clutches of about:config dragons isn't very nice.

To not deactivate in the first place: uncheck the "disable" checkbox when the dialog pops up about it.
To reactivate if you've mistakenly deactivated it by not paying attention and just auto-clicking the button to continue, you can simply re-enable in the add-on manager.

[illiad]

may i ask, will 'YESscript' do what is wanted?? I have loads of PQIs thanks to FEBE..