Is Mendeley Referencer safe?
Mendeley Referencer embeds its Mendeley OAuth client secret and sends it to api.mendeley.com during login.
The extension includes a Mendeley OAuth client secret in its installed JavaScript files. During the login and token refresh flows, it uses that secret in a Basic Authorization header sent to Mendeley's token endpoint.
Who publishes itdnibnzbckr - 1 other listing from the same operator, 1 of them carrying a finding
dnibnzbckr - 1 other listing from the same operator, 1 of them carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
1 other listing published from this account, 698 users between them. 1 of them carries a finding.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 0.5.9. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
<all_urls>
Store data in your browser
storage
Act on the current tab, but only after you click the extension
activeTab
Sign you in with your Google account
identity
See the address and title of every tab you have open
tabs
Where it sends data
Destinations our analysis observed Mendeley Referencer contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- api.mendeley.com
Mendeley Referencer sends data to api.mendeley.com. One other extension we have analysed sends data here.