Sushi Bytes

AI didn’t just change how you build software, it broke your process for inspecting it for open source license compliance and security vulnerabilities.In this episode of Sushi Bytes, Shinobi and Gen reconnect with Aaron Branson to unpack FossID’s newly announced Agentic SCA strategy – and why the timing couldn’t be better after our last conversation on SCA in the AI Era.As code generation accelerates and the sheer volume of code explodes, software risk leaders are facing a new reality: more code, more complexity, and less time to react. Aaron breaks down how Agentic SCA shifts the process from passive scanning to active participation – embedding intelligence, automation, and policy enforcement directly into the development workflow.If you’re dealing with AI-generated code, SBOM pressure, or stepping up compliance rigor without slowing developers down – this is the conversation you need right now.

AI is changing how software gets written – but what does that mean for open source compliance and software supply chain security?In this episode of Sushi Bytes, Shinobi and Gen explore SCA in the AI era. As development shifts from prompts to autonomous agents, tool-augmented workflows, and spec-driven engineering, traditional software composition analysis workflows need to evolve.They break down the three major shifts in AI-assisted development and explain why SCA tools must become agent-friendly, tool-driven, and embedded directly into modern development pipelines.If AI is writing the code, someone still needs to understand what’s in it.

For years, Software Composition Analysis focused on managing open source consumption and the related legal and security risks – and that was enough. Today, it isn’t.In this episode of Sushi Bytes, Shinobi and Gen sit down with Aaron Branson to unpack why SCA must evolve to meet modern software realities: AI-generated code with unclear provenance, developers contributing back to open source without leaking IP, and regulations like the EU CRA that demand trustworthy, scalable SBOMs.The takeaway? SCA delivers far more ROI when it’s used to manage today’s risks – not yesterday’s assumptions.

In the first episode of Sushi Bytes Season Two, Shinobi and Gen welcome Gary Armstrong, Senior Director of Customer Success at FossID, for a practical conversation on what the CRA really requires in 2026 and 2027. Based on Gary’s recent whitepaper, Software Supply Chain Integrity and SBOM Obligations under the EU Cyber Resilience Act, this episode cuts through the noise to explain what you need to do now to be ready.

Startups are moving fast – fueled by AI-generated code, experimental “vibe coding,” and a breakneck pace of shipping software. But when those startups become acquisition targets, things can get messy. In this episode, Shinobi goes solo (with Gen temporarily sidelined by a network outage) to unpack how this new wave of coding introduces license risk that traditional SBOMs miss. Learn why SCA-powered software audits are essential for surfacing modified open source fragments, how blind audits protect confidentiality, and why acquirers need more than metadata to see what’s really lurking in a target’s repo. 

The EU Cyber Resilience Act (CRA) is reshaping global expectations for software security – and putting Software Bill of Materials (SBOMs) at the center of compliance. In this episode, Shinobi and Gen break down what the CRA requires, how it compares to U.S. regulations, and what engineering and legal teams must do now to stay ahead. Whether you're shipping to Europe or just want to future-proof your software supply chain, this episode will help you understand what a complete, compliant, and consumable SBOM really looks like. 

Developer experience and productivity are critical, but so is copyright and license compliance. In this episode of Sushi Bytes, Shinobi and Gen talk about the tug-of-war between productivity-centric engineering teams and risk-averse legal teams. Who will win? Tune in to hear how modern SCA tooling can align speed with safety, automate away this friction, and give both devs and compliance leaders what they need to ship fast without introducing intellectual property and other legal risk.

Not every Software Composition Analysis (SCA) tool reveals what’s really haunting your code. In this Halloween-themed episode of Sushi Bytes, Shinobi and Gen explore why comparing SCA tools is trickier than it seems—and what engineering and compliance teams should look for under the mask. From snippet detection and modified code to license clarity, SBOM formats, and audit readiness, this episode offers a practical guide to choosing an SCA partner that’s built for the complexity of modern software supply chains. Light on fear, heavy on insight- this one’s a treat.

In this episode of Sushi Bytes, Shinobi and Gen unpack the high-stakes reality of code snippet: when small fragments of open source code make their way into proprietary applications and go undetected by traditional SCA tools.From copy-pasted Stack Overflow answers to AI-generated code functions, these sometimes-small code segments can carry serious licensing obligations. Learn why simplistic dependency analysis tools miss them, how sophisticated snippet detection technology catches them, and what engineering and compliance leaders can do to reduce hidden IP risk… especially in embedded systems, regulated environments, and during M&A.

AI-assisted coding is accelerating development, but also creating compliance headaches. In this episode of Sushi Bytes, Shinobi and Gen unpack the legal gray zones around AI-generated code: Who owns it? Is it safe to use? What happens if it’s trained on GPL-licensed data?If your team uses GitHub Copilot, ChatGPT, or Claude, there’s a good chance your codebase already includes AI-generated snippets—with no license, no attribution, and no paper trail. This episode explores how to identify that risk, build smart internal policies, and scan your way back to clarity.

In this episode of Sushi Bytes, Shinobi and Gen dive into the hidden risk of license drift – when the open source license declared in metadata files like package.json or README doesn’t match the actual licenses embedded in the source code. It’s a common problem with serious consequences, especially in embedded systems or M&A deals. The duo explores why relying on metadata alone can mislead engineering teams and expose organizations to IP risk, and how SCA tools like FossID catch mismatches through file-level inspection – so you don’t ship surprises with your software.

Not every vulnerability in your SBOM is a real threat. That’s where VEX comes in. In this episode of Sushi Bytes, Shinobi and Gen explore the Vulnerability Exploitability eXchange… what it is, why it matters, and how it helps teams focus on the vulnerabilities that actually matter. From cutting through alert fatigue to avoiding the growing mess of BOM spinoffs, this duo keeps it sharp, practical, and just a little snarky.Want fewer false alarms and more actionable intel? VEX marks the spot.

Your software has a supply chain. Your SBOM is supposed to tell you what’s inside. But what makes a Software Bill of Materials truly useful; and why is everyone suddenly asking for one? In this episode of Sushi Bytes, Shinobi unpacks what an SBOM is, why regulatory pressure is turning it from best practice to business-critical and why spinning off “AI-BOMs” and “API-BOMs” just adds noise. Software is software. Let’s keep it simple… and get it right.

Welcome to Sushi Bytes – FossID’s bite-sized, AI-generated podcast hosted by Shinobi, your sharp-eyed Software Composition Analysis ninja. In this debut episode, Shinobi breaks down what “software supply chain integrity” really means… and why it’s now a board-level concern. From open source license compliance to AI-generated code and SBOMs, we explore the risks hiding in your codebase and the strategic steps to stay ahead. Short. Smart. No fluff. Let’s get slicing.