<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Entropic Drift</title><link>https://entropicdrift.com/tags/security/</link><description>Recent content in Security on Entropic Drift</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>glen@entropicdrift.com (Glen Baker)</managingEditor><webMaster>glen@entropicdrift.com (Glen Baker)</webMaster><copyright>© 2026 Glen Baker</copyright><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://entropicdrift.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Debtmap Adds Go and Solidity Support for Web3 Code Review</title><link>https://entropicdrift.com/blog/debtmap-solidity-web3-security/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><author>glen@entropicdrift.com (Glen Baker)</author><guid>https://entropicdrift.com/blog/debtmap-solidity-web3-security/</guid><description>&lt;p>&lt;a
href="https://github.com/iepathos/debtmap"
target="_blank"
>Debtmap&lt;/a> started from a practical thesis: bugs tend to correlate with certain kinds of code.&lt;/p>
&lt;p>Not perfectly. Not mechanically. But enough to be useful.&lt;/p>
&lt;p>Complex functions are easier to misunderstand. Frequently updated files are places where design pressure is still active. Historical bug hot spots are worth treating with suspicion. Low test coverage makes changes riskier. Code that developers avoid touching often has reasons for being avoided.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://entropicdrift.com/blog/debtmap-solidity-web3-security/feature.jpg"/></item></channel></rss>