Is Xbrl signing safe?
Xbrl signing forwards certificate and signing requests from scoped pages to a local native signing app.
On localhost, XBRL-related domains, and file pages, the extension exposes page functions for certificate, signing, and version requests. Those requests are passed through the extension to the installed native messaging host named xbrl.signing, so the local signing app receives the signing-related data from those pages.
Who publishes itLOGIC INFORMATIQUE - no other listings under this identity, 1 shared hostname
LOGIC INFORMATIQUE - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
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 3.0.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Talk to a program installed on your computer, outside the browser's sandbox
nativeMessaging
Where it sends data
Destinations our analysis observed Xbrl signing 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.
- xbrl.signing
Xbrl signing sends data to xbrl.signing. No other extension we have analysed sends data here.