Given that this was:
(a) In an official github repo from the organization
(b) The announcement was made by the co-founder and CTO
It would need to be a complex set of circumstance for apparent authority to NOT apply. I can come up with such circumstances which might apply, but it would have to be a lot more than just saying they didn't authorize their CTO to do this. If you can't take the statements of a CTO at face-value, the world of business would collapse.
(And to re-emphasize: I am not a lawyer. "In my law class" should not convey I went to law school, and taking a couple of law classes does not a lawyer make).
I had read into "After DDN’s acquisition ... subsequently improperly open sourced ... without DDN’s permission" to mean that the code had been acquired from another entity, but then someone associated with that entity which no longer had any rights to the code released it as open source.
The agency criteria is much narrower and easier to challenge.
The article also indicates "The agent must have been held out by someone with actual authority to carry out the transaction and an agent cannot hold himself out as having authority for this purpose." Which makes it seem that EdgeFS would not be bound to any actions taken by someone who they had never presented as having the authority to take those actions.
So, very complex here, and appears that the issue of apparent authority is largely bound to a lot of other factors, not just association or lack thereof.