The usb backdoor used to access scanner is called the SANE project is in this code: https://gitlab.com/sane-project/backends/blob/master/backend/canon_dr.c
"Smartmatic www.smartmatic.com provided testing and changes for DR-X10C support"
proof georgia used the scanner:
https://sos.ga.gov/admin/files/Unisyn%20RFI_Redacted.pdf
you can also see how much the scanner was used last election here:https://www.sos.state.co.us/pubs/elections/VotingSystems/audits/2014GeneralPEA/Delta2014GeneralPEA.pdf
You can see in the comments the developers didn't want to credit smartmatic: https://gitlab.com/sane-project/backends/-/merge_requests/12#note_139722740
The sane project is in an open source API stack, a 20 year old project with hundreds of people and companies submitting commits just like in any open source project.
Don't spread conspiracy theories.
But why did smartamatic add support for the DR-X10C ballot scanner in the last year? Why would they make changes to add a ballot scanner into 20 year old code that can be used as a usb backdoor to change results. Have you looked at the code and seen what the SANE project is capable of?
I know the project and looked at the commit:
https://gitlab.com/sane-project/backends/-/commit/81faeb46f28c4b6c251123aabac118ff0262d9e7
This just adds support to the scanner they are using in their machines, which you can assume is the same model across all of them for compatibility reasons.
There are no backdoors whatsoever in the code, no I/O or network sockets, or any user controlled input.
And no, the sane project is not a USB backdoor of any kind. When you want to plant a backdoor into a piece of open source code, you fork it, make the changes and install it on your machines. You don't submit a patch upstream for the whole world to see.
There's no evidence of smartmatic using DR-X10C ballot scanner only dominion. They probably hired freelancers to make it compatible. If you don't think SANE can be used as a backdoor you should read more into SANE: https://sane-project.gitlab.io/standard/