Add VirusTotal scan results to add-on details#18974
Conversation
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
This is a great improvement, thank you Sean for this nice work. |
|
@Adriani90 - add-ons are scanned when they are submitted to the store. You should be able to view the scan results before updating. |
Co-authored-by: Sascha Cowley <16543535+SaschaCowley@users.noreply.github.com>
Qchristensen
left a comment
There was a problem hiding this comment.
Reads well. Showing VirusTotal results is a good inclusion for user peace of mind.
It is also worth noting that the new warning text is not in response to any incident or malicious add-on, but simply ensuring users are aware of the scope of access add-ons have always had. We have a robust and healthy add-on ecosystem - their power can make them very useful, but it is important to be aware of their potential access before downloading particularly from an unknown source.
Fixes #18991 Fixes a bad merge conflict fix between #18816 and #18974 Summary of the issue: add-on store cannot open Description of user facing changes: add-on store can open again Description of developer facing changes: none Description of development approach: fix merge conflict Testing strategy: add-on store can open again
Fix-up of #18974 Summary of the issue: One newly translatable string needs to support plural forms: "{malicious} out of {total} malware scanners detected this add-on as potentially malicious." In English, there is no difference, since "detected" uses the same form at singular or plural; but in other languages, not. There are also languages where scanners pluralization needs to change. Description of user facing changes: The information will have correct pluralization form. After discussion, I have tried to find a wording where only one of the two numbers needs an agreement to avoid splitting and re-building the sentence. Description of developer facing changes: N/A Description of development approach: Use npgettext instead of pgettext.
Link to issue number:
Replaces #16510 and #16316
Related discussion #16241
Summary of the issue:
Description of user facing changes:
Description of developer facing changes:
None
Description of development approach:
Testing strategy:
Known issues with pull request:
None
Code Review Checklist: