Mallory Bowes-Brown

> If its used todo security assessments, then it can be added ;) Technically, when used w/the shell script, it's a security assessment. But just for the user's local Chrome...

I'll add these to the lists later tonight. Thanks for the pointers!

Been doing a bit of thinking about this and I think I'm going to create a second file that will have the per-record metadata. I'm kinda liking the approach of...

Absolutely great points. I've been putting off the go-back-and-match-the-extension step of the metadata creation since it'll be a pain. But ultimately, it might have some value for ppl so I'll...

Eh... I gots nothing better to do... :-) Like everyone else, covids has me locked in my place and working on populating the metadata will prolly be the only thing...

Starting to think I should add a field for "reported malicious" for those extensions that are in a non-confirmed state. (See the latest Kaspersky alert and Great Suspender extension stories)...

> If you create the metadata file, create the structure, and populate all of the IDs, we can collaborate on the metadata collection and chip away at it over time....

> From here on out, I'll populate both lists: the list of just extension ids and the list with the metadata. Also, for right now, I created two discrete fields...

Contributor @blauwers added support for Mac to the current script in the repo. Windows still needs to be done.

> _chanting Windows! Windows! Windows!_ Lol. I've thought about making an attempt to flail "The Worst Powershell Script Ever Written" together (since Windows is def not my AoE) but I'm...