Wow, this looks pretty damning. I can't imagine Google seeing this as worth the risks. Is an innocent explanation possible here?
Wow, this looks pretty damning. I can't imagine Google seeing this as worth the risks. Is an innocent explanation possible here?
This is normal (specific to pyproject.toml overwriting authors). I am not sure about pyproject.toml conventions but I would have done the same. This is the equivalent of telling you who the maintainers of the project are.
Usually what you see in the code is the retention of Copyright statements on source code and LICENSE with some reference on README.
The lack of any attribution at all is the ultimate issue like you point out, but the force push demonstrates intent over honest mistake in my opinion.
Might makes right, and these companies have more power than a whole raft of nation states. They act with complete assurance that absolutely nothing will come of it.
Maybe it is possible the google engineer didn't understand how open source licenses work, or didn't care since maybe it was supposed to be an internal project first that eventually ended up open sourced?