<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Mythos on BeLibre - Belgian independent knowledge and policy platform</title>
    <link>https://belibre.be/en/tags/mythos/</link>
    <description>Recent content in Mythos on BeLibre - Belgian independent knowledge and policy platform</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
    <lastBuildDate>Fri, 15 May 2026 11:00:00 +0100</lastBuildDate><atom:link href="https://belibre.be/en/tags/mythos/index.xml" rel="self" type="application/rss+xml" /><item>
      <title>FOSS just passed Mythos&#39; stress test</title>
      <link>https://belibre.be/en/blog/policy/mythos-challenge/</link>
      <pubDate>Fri, 15 May 2026 11:00:00 +0100</pubDate>
      
      <guid>https://belibre.be/en/blog/policy/mythos-challenge/</guid>
      <description>&lt;hr&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; In April, Anthropic announced an AI model called Mythos that had reportedly found thousands of serious security bugs in every major operating system and web browser. The reaction was loud: The Bank of England warned regulators it could &amp;ldquo;crack the whole cyber risk world open&amp;rdquo;, US Treasury called in the big banks, NHS England closed all its public code repositories inside two weeks.
Five weeks on, the dust has settled and the picture looks different: Independent reviewers pulled the headline numbers apart. The creator of curl, one of the most widely used open-source tools in the world, ran the Mythos report against his own code and found it had identified one minor flaw, calling the hype &amp;ldquo;primarily marketing&amp;rdquo;. 99% of Mythos&amp;rsquo;s claimed findings remain unpublished and unverified.
What did happen in those five weeks is that the open-source world fixed and disclosed its share of the bugs publicly, in the open, on commit logs anyone can read. That is open source working as it is supposed to, so don&amp;rsquo;t call open-source a liability.
The lesson for our administrations is the opposite of NHS England&amp;rsquo;s. Closing your code does not make you safer. Funding the open ecosystem you already depend on, and using similar AI tools defensively on your own code, does.&lt;/em&gt;&lt;/p&gt;</description>
      <media:thumbnail url="https://belibre.be/images/belibre_ico_180.png"/>
    </item>
    
    <item>
      <title>BeLibre Sovereignty Map</title>
      <link>https://belibre.be/map/</link>
      <pubDate>Mon, 01 Jan 2026 00:00:00 +0000</pubDate>
      <generator>Hand crafted</generator>
      <guid>https://belibre.be/map/</guid>
      <description>Interactive map where you can discover digital sovereignty in municipalities, schools, emergency services or other critical infrastructure in our country and beyond.</description>
      <media:thumbnail url="https://belibre.be/images/belibre_ico_180.png"/>
    </item>
  </channel>
</rss>
