\n<\/p>\n
Google is adding a new feature to the next release of Chrome that will proactively alert you when an extension isn\u2019t in the Chrome Web Store, according to a post<\/a> from Oliver Dunk, a developer relations engineer for Chrome extensions. The new feature, being added as part of Chrome 117, will make it easier to stay on top of extensions that have been removed by a developer, been taken down for violating the Chrome Web Store policies, or been marked as malware.<\/p>\n<\/div>\n Dunk says Chrome will show extensions that fall under those categories in a \u201cSafety check\u201d section in the privacy and security part of Chrome\u2019s settings. \u201cWhen a user clicks \u2018Review,\u2019 they will be taken to their extensions and given the choice to either remove the extension or hide the warning if they wish to keep the extension installed,\u201d Dunk explains. \u201cAs in previous versions of Chrome, extensions marked as malware are automatically disabled.\u201d <\/p>\n<\/div>\n That\u2019s not the only security-related update Google discussed for Chrome on Wednesday. The company is going to automatically upgrade all http:\/\/ URLs to https:\/\/, the more secure version of HTTP<\/a> that encrypts your traffic, \u201ceven when you click on a link that explicitly declares http:\/\/,\u201d according to a separate blog post<\/a>. Google says it will detect when the attempted upgrades don\u2019t work, and when that happens, Chrome will fall back to http:\/\/. Google is \u201cexperimenting\u201d with the change in Chrome 115 (Chrome 116 is the current stable release). The company plans to roll it out to everyone \u201csoon.\u201d<\/p>\n<\/div>\n Google also says that Chrome will soon show a warning when you try to download \u201chigh-risk files\u201d while on an insecure connection. The warnings are set to roll out in mid-September, and you can see Google\u2019s example image of what they will look like below.<\/p>\n<\/div>\n