We need MAXIMUM transparency into these voting machines, and the best way to do that is for all voting machine companies to open source their applications that directly handle ballots. Like repos publicly viewable on Github and version control managed by the Federal Election Commission.
This way those of us that understand the arcane magic of C, C++, Java, and Python (among others) can throw our expertise in analyzing and securing critical election software by ripping out these Democrat backdoors like what we found in Michigan.
Maybe we should not use software.
We had 250 million people and wrapped up voting and counting in time for the 11pm news to report the results. No computers. Just telephones, sheriffs, and sworn & signed papers by people who would go to jail if the numbers were wrong. The mechanical machines could not be rigged. The paper voting used boxes sealed by the sheriff at 7am and unsealed by the same sheriff at 7pm. All who wanted to watch the opening of the box could and also watch the counting. On each side of the counter was one D and one R, rarely also an I. Each person looked at the ballot and agreed on the vote. All in front of everyone watching. It was easy to count 300 votes an hour that way....about the size of each voting location.
I'd say the same thing for twitter, youtube, and google.
They need the code audited too.
As long as you're referring to proper code signing and validation, I'm all for that. Let's not let the government try to reinvent the wheel, but rather use off the shelf solutions that are known good.