Is Inclusive Code Comments safe?
Inclusive Code Comments sends text typed in editable fields to api.languagetool.org for grammar checking after opt-in.
The extension runs on all pages and wraps editable fields. Once the user accepts a privacy confirmation (off by default), the typed text is sent to LanguageTool's servers for grammar checks, and selected words with surrounding text are sent to its synonyms service. This is the extension's stated grammar-checking purpose.
Who publishes itJonathan Peppers - no other listings under this identity, 2 shared hostnames
Jonathan Peppers - no other listings under this identity, 2 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 2 hostnames
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 Inclusive Code Comments 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.languagetool.org
Inclusive Code Comments sends data to api.languagetool.org. 3 other extensions we have analysed send data here.
- synonyms.languagetool.org
Inclusive Code Comments sends data to synonyms.languagetool.org. No other extension we have analysed sends data here.