As a general feedback: I'm a bit cautious about using third party Chrome extensions. I'm more OK with giving auth to my LinkedIn account. Maybe a server side option with headless chrome would be a good addition.
What is it about third-party extensions you don't like?
I know many extensions have full access to any site you visit, but I specified LinkedIn for mine, so when you install it, you are warned that it can access all your data on LinkedIn, but no other sites.
On Chrome extensions, minor bugs (or minor bugs in the libraries you depend on) might end up having far worse consequences. Read/write access to only linkedin.com can still leak a decent amount of unwanted information in case there's an exploit.
I don't use any external libraries, I wrote all of the code in the extension, and the only external requests made outside of the extension are to Google Fonts, so I wonder if it'd be possible to infect this extension.
As a general feedback: I'm a bit cautious about using third party Chrome extensions. I'm more OK with giving auth to my LinkedIn account. Maybe a server side option with headless chrome would be a good addition.