The Good Tech Companies - Insignary Launches Clarity AIR to Detect Undeclared Open-Source and AI-Written Code

Episode Date: October 8, 2026

This story was originally published on HackerNoon at: https://hackernoon.com/insignary-launches-clarity-air-to-detect-undeclared-open-source-and-ai-written-code. New snippet-level scanning shows security and compliance leaders which open-source code and which AI-written code never made it into a manifest. Check more stories related to undefined at: https://hackernoon.com/c/undefined. You can also check exclusive content about #cybersecurity, #cyber-threats, #press-release, #cyber-security-trends, #cybercrime, #cybersecurity-awareness, #cybersecurity-tips, #good-company, and more. This story was written by: @cybernewswire. Learn more about this writer by checking @cybernewswire's about page, and for more stories, please visit hackernoon.com. Insignary has launched Clarity AIR, a source-code scanning product that identifies open-source code and AI-written code not declared in manifests, closing a blind spot in software security. Clarity AIR finds unknown open-source code, detects AI-written code, and inventories AI dependencies, producing audit-ready SBOMs and full reports.

This audio is presented by Hacker Noon, where anyone can learn anything about any technology. Insignary launches Clarity Air to detect undeclared open source and I-written code by Cyber Newswire. Toronto, Canada, October 8, 2026, Cyber Newswire, Insignary launches Clarity Air. Closing the blind spot between what your developers declare and what's actually in your code new snippet level scanning shows security and compliance leaders which open source code and which AI-ridden code never made it into a manifest. Insignory Inc. today announced the general availability of Insignary Clarity Air, a source code scanning product built to answer a question most security teams can't currently

answer with confidence. What is actually running in their software, beyond what developers reported. Manifests and SBOMs built from declared dependencies are only as complete as what developers chose to report. An estimated 70 to 90% of applications today are built substantially on open source code and a meaningful share of it arrives through channels no manifest captures, a function copied from another project, a snippet pulled from a forum, a block and AI coding assistant generated and nobody reviewed line by line. For a CISO signing off on an SBOM or a legal team certifying license compliance, that gap is unmanaged risk sitting inside a document meant to prove the opposite. Clarity error is built to close it at the source code level rather than the

manifest level. It finds open source your manifest doesn't know about matching source code against insignery's fingerprint database of the open source ecosystem. Even when the code has been modified, adapted, or regenerated, which is exactly what happens when AI assistants touch it. It tells organizations how much of their code base and AI actually wrote, classifying code line by line with a confidence score, so engineering, security, and legal can see AI assistant output as a distinct risk category instead of an invisible one. It inventories the AI your software depends on the models, APIs, and frameworks built into the product itself, producing an AI bill of materials alongside the standard open source one. Every match is reviewed and confirmed by a human before it's counted,

and results export as audit-ready SBOMs and full reports. You cannot verify an SBOM by reading the manifest that created it. AI-written code is the same problem. If a developer does not declare it, nothing records it, you have to look at the code itself, said Taek Juan Kim, president and CEO of Insignary. Current compliance context T for CSOs, the compliance calendar just accelerated across North America, unevenly, which is its own risk. In the U.S., arms January 2026 update, Memorandum M2605, pushes federal agencies toward independently verifying vendor SBOMs rather than relying on a single attestation form, and FDA Section 524B remains a separate binding requirement for every cyber device submission. In Canada, Bill C8 made the Critical Cyber Systems Protection Act law in June 2026,

with supply chain obligations now phasing in. None of this converges into clean rule, which is exactly why an inventory built only on what developer shows to declare is so fragile to defend whichever side of the border you're on. Clarity error joins insignery Clarity. the company's binary level software composition analysis platform, and Clarity SC, its SBOM governance platform, in the Insignary Clarity Suite, giving security and compliance teams coverage from source code through compiled binaries to SBOM lifecycle management. Availability Clarity Air is available now directly from Insignary and through its partner channel, deployed on customer-owned infrastructure. Trial licenses are available on request at insignory.com, a free, easy-to-use-use demo of the

AI code detection capability is also available at Insignory.com for anyone to try. About Insignory Insignory, Inc. is a Toronto-based software supply chain security company. Its patented binary fingerprint technology lets enterprises, government agencies, and software vendors verify what's actually inside the software they build, ship, and deploy, directly from compiled binaries, without needing source code. Insignary has been cited in four Gardner Research Reports and named a sample vendor for reachability analysis in the Gartner hype cycle for secure software engineering, 2026. The company is supported by strategic partners including Bering Point in Europe,

Cybertrust Japan and Tech Matrix in Japan, and TMA Solutions. Contact Principal Solutions architect Jessica Dai Lee Insignory, inc.jsigali at insignery.com this story was published as a press release by CyberNewswire under Hackernoon Business Blogging Program. Thank you for listening to this Hackernoon story, read by artificial intelligence. Visit hackernoon.com to read, write, learn and publish.