I know the permissions are overbearing. The reason it requests permissions for all sites instead of just the supported players is because of the way Chrome updates extensions. If I were to go that route and at some point add another player (which happens often), Chrome would disable the extension for everyone until they re-approve the changed permissions.

I believe there is a way to do it dynamically and allow the user to choose which players they want to allow access to, and then accept the changed permissions. However a majority of my user base will not care, and would actually prefer the one click install ease of use. At least that's my reasoning.

For those of you really concerned, you can download the source and modify manifest.json to change where the contentscript is injected for peace of mind. https://github.com/kkamperschroer/Musicality

Right off the bat, I spent 5 seconds looking at the plugin page and wasn't immediately sure what the plugin does. There's a list of features starting with "Playback Controls" and "Now playing information"... I assume it's a music player maybe? I'd suggest working up a short, succinct sentence that explains in very simple terms what the plugin does and make sure it's the thing I first see!