Is GoingMed safe?
GoingMed sends journal names, PubMed IDs, and DOIs from academic pages to publication lookup services.
On PubMed, Google Scholar, Semantic Scholar, PubPeer, and PMC pages, GoingMed reads article metadata from page content and URLs as results or details load. It sends journal or venue names to GoingPub for impact-factor lookups, and sends PubMed IDs or DOIs to PubPeer and OpenCitations to add comment and citation links.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itmikertan - 1 other listing from the same operator, none carrying a finding
mikertan - 1 other listing from the same operator, none 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, 2k+ users between them, none of them carrying 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.
Where it sends data
Destinations our analysis observed GoingMed 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.
- pubpeer.com
GoingMed sends data to pubpeer.com. 3 other extensions we have analysed send data here.
- api.opencitations.net
GoingMed sends data to api.opencitations.net. No other extension we have analysed sends data here.
- goingpub.com
GoingMed sends data to goingpub.com. No other extension we have analysed sends data here.