Reported violations of the Code of Conduct are sent to a Steering Committee, made up of members of the community, who determine if the reported project is in violation of the Code of Conduct. If so, the Committee takes steps to remedy the situation (e.g. realigning project with the Code of Conduct, or removing ml5.js from the project) — and if no resolution is found, the project falls out of compliance with the terms of the software license.
It's an interesting experiment.² Software is a tool to help us solve problems and reach desired outcomes. Licenses are also a tool to help us solve problems and reach desired outcomes. When desired outcomes exclude certain things (e.g. discrimination of marginalized communities, manipulation of public opinion, autonomous weapons, values antithetical to that of a community), it seems a Code of Conduct can also be a worthwhile tool to solve problems and support the outcomes that the community is working towards. (Of course, wisdom and governance are crucial and not to be taken for granted. Shout out DKP servers³ for showing some light there.)
¹ ml5.js Code of Conduct: https://github.com/ml5js/Code-of-Conduct/
² Analysis from KE Mitchell on ml5.js licensing: https://writing.kemitchell.com/2021/01/12/ml5js-Takes-a-Stan...
³ On Dragon Kill Points and governance systems in World of Warcraft: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=958945