Ruby allows to re-open any class and re-implement or override methods.
Gems under supply chain attack can re-open standard library classes, re-implement frequently used methods and start recording or logging important data (say Net:HTTP library’s GET/POST calls).
How do we freeze
standard library classes such that the process crashes or throws warning when some rogue gem tries to re-open/re-implement them?
Does ruby (or) rails community address this concern in any way today?