Not a big fan of the title (asking question in the title isn’t a great idea) but the conclusions give a good summary:
The Cyber Resilience Act (CRA) represents a significant step in Europe’s efforts to enhance cybersecurity. However, its potential implications for the open source software community have raised serious concerns. Critics argue that the legislation, in its current form, could impose undue burdens on open source contributors and inadvertently increase the risk of software vulnerabilities being exploited.
New insights from GitHub’s blog post highlight additional concerns. The CRA could potentially introduce a burdensome compliance regime and penalties for open source projects that accept donations, thereby undermining the sustainability of these projects. It could also regulate open source projects unless they have “a fully decentralised development model,” potentially discouraging companies from allowing their employees to contribute to open source projects. Furthermore, the CRA could disrupt coordinated vulnerability disclosure by requiring any software developer to report to ENISA all actively exploited vulnerabilities within a timeline measured in hours after discovering them.
No it doesn’t. It makes IBM responsible for what it ships in Red Hat, it doesn’t apply to someone that made some library in their weekend that somehow ended up on all Linux distributions.
That may be the intent, but laws have side effects and bureaucrats are all too eager to enforce them.