It's a fair point that it's still up, though looking just now for two minutes there are at least some issues with auth[1] which would make me really not trust it.
It was just speculation about what could be bad enough if they really did have permission to release it, but the OP is being so cagey below now I'm just wondering if they got release permission but misrepresented what they would be releasing or something.
> and is official [1]
FWIW no idea what you're trying to point out on that page unless you mean the one link to a different project in the same github org indicates the org is official, but that never seemed in doubt in this thread of comments.
> If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository.
Unclear what you're referring to here. Was it "misrepresented what they would be releasing"?
If that's the case, I disagree that the repo still existing is on its face evidence against that theory. It could be a perfectly fine tool, but if you lie on a release checklist, depending on what you lie about, it's easy enough to imagine a fireable offense. There are multiple ways that "it's easier to ask forgiveness" can backfire if there are legal things or organizational things you are knowingly avoiding.
Again, this is just speculation. I wouldn't personally fire someone for releasing a library that got popular, but its also speculation to suggest that's the only reason he was fired.
Maybe at this point it's even more disruptive to delete it since people are using it. There's a real reason to not want someone to release an official-looking CLI when you're already doing an actual official one for the same thing.
Idk if the firing was justified since he supposedly followed process and had manager approval, but that's only one side.
[1] https://developers.google.com/workspace/drive/api/samples