Firefox unsigned/signed and two versions of NoScript?

[Gari]

I am using Firefox 40.0b3 beta Win-64 with development build NoScript 2.6.9.30rc4 and was automatically updated to development build NoScript 2.6.9.30rc5 and shows that this new version build was signed; however, upon updating to the stable version NoScript 2.6.9.30, now it shows NoScript could not be verified as signed.

I also noticed upon clicking on "Get Add-ons" and searched for "NoScript" and clicking on "see all 31 results" link, it doesn't show "NoScript" by itself but rather a different "NoScript Security Suite." So, what's the difference between the "NoScript" that I am currently using and the "NoScript Security Suite" now showing on Firefox Add-ons? Please clarify.
- Thanks.

[barbaz]

So, what's the difference between the "NoScript" that I am currently using and the "NoScript Security Suite" now showing on Firefox Add-ons?

The only difference is the name showing on Firefox Add-ons.
viewtopic.php?f=8&t=14220

The rest of the stuff you mentioned wasn't a question, but here's sort of an answer anyway: it's just part of a bunch of chaos going on at AMO with them trying to roll out this signing requirement for Firefox add-ons, and yes that whole deal is going to be chaotic and a mess for a while...

[Gari]

@barbaz. Thanks for clarifying!

[barbaz]

You're welcome

[therube]

upon updating to the stable version NoScript 2.6.9.30, now it shows NoScript could not be verified as signed

Updated how, from where?
If it comes from AMO, I'd expect it to be signed, & working correctly (barring some error on AMO's side).

If it comes direct from here, AFAIK, last time I looked, it would not be signed.