<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sandbox</title><link>https://blog.ast.moe/en/tags/sandbox/</link><description>Recent posts: Gorimuchu</description><generator>Hugo</generator><item><title>What can be done with Izanagi</title><link>https://blog.ast.moe/en/blog/2026-10-08-3/</link><pubDate>Thu, 08 Oct 2026 22:24:12 +0900</pubDate><guid>https://blog.ast.moe/en/blog/2026-10-08-3/</guid><description>&lt;p&gt;When you run &lt;code&gt;npm install&lt;/code&gt;, it not only downloads the package but may also execute scripts that the package provides. If you run that code in your regular development environment, you can access files readable by the executing user and the environment variables passed to the process.&lt;/p&gt;
&lt;p&gt;To isolate such development commands and track what they access, we have built Izanagi in Rust (&lt;a href="https://github.com/ieee0824/izanagi"&gt;source&lt;/a&gt;). It records file accesses, network communications, and child‑process launches so you can examine the behavior of the executed code.&lt;/p&gt;</description></item></channel></rss>