RunSafe closed out Q3 with a number of big additions to the RunSafe Security Platform, including major new features for both GitHub support and license compliance.

Here’s what’s new in October:

• The RunSafe Security Platform: GitHub support now available!
• Identify: New license compliance feature
• Identify: Git submodule detection
• Identify: Windows dependency mapping
• Protect: LynxOS-178 integration now available

RunSafe Adds GitHub Support!

Customers can now integrate their GitHub projects with the RunSafe Security Platform! This major update allows you to receive automatic Software Bill of Materials (SBOM) generation and integration with RunSafe Protect.

After installing our app on GitHub.com, you’ll have access to the RunSafe Security Platform. Once you’ve created an account, you can select which projects you would like to apply RunSafe Identify or RunSafe Protect to. 

For Identify, after selecting your repositories, we automatically add a RunSafe scan into a GitHub workflow. Now, every time you push code, RunSafe will automatically generate an SBOM. You can select the links within GitHub to then view the SBOMs within the platform alongside vulnerability information. When you configure Protect, you will get Protect Source integration at C++ build time.

Learn more about the RunSafe Security Platform.

New License Compliance Feature Helps Prevent Copyleft Risk

We rolled out a major new feature in the RunSafe Security Platform for license detection and compliance. The license compliance feature allows customers to configure organization-wide rules to stop the delivery of code licensed under unwanted terms, automatically alerting or blocking builds containing disallowed licenses. 

The feature is particularly useful for companies needing to prevent “copyleft” licenses, which can legally require them to open-source their proprietary code if they inadvertently pull in code with licenses that are too permissive. With this update, you can easily decide which licenses are safe, which ones are off-limits, and how you want your build pipelines to react when something slips through.

Unlike complex alternatives that require extensive manual configuration, RunSafe’s approach offers a balanced mix of control and simplicity. Whether you want to automatically fail builds that include banned licenses or just get a friendly heads-up, it’s configurable to your comfort level. As your team adds new dependencies, RunSafe automatically tracks and flags any new or “unset” licenses.

The feature also complements our SBOM generation capability with quality license detection, especially for C++. Overall, our goal is to give organizations greater control and confidence in managing open-source license compliance.

RunSafe Identify Adds Package Detection Through Git Submodules

RunSafe Identify now supports package detection through Git submodules, expanding our ability to identify and track software components in complex C/C++ projects. 

Defining packages in C/C++ is challenging. By adding Git submodules support, we’ve enabled detection of both direct and recursive submodules, whether they reference internal or external repositories. 

We’re also able to automatically extract key details, such as name, version, CPE, and PURL, enhancing accuracy and completeness in SBOM generation.

For more on the challenges of dependency management approaches in C/C++, Kelli Schwalm, Director of SBOM at RunSafe, discusses more in this blog on “The Wild West of C/C++ Development & What It Means for SBOM Generation.”

Windows Dependency Mapping Added to RunSafe Identify

We’ve expanded our SBOM generation capabilities within RunSafe Identify to include dependency mapping for Windows environments. Previously available only for Linux, this feature now allows users to visualize how software components depend on one another across Windows builds. The new functionality aligns with CycloneDX version 1.6 standards.

Learn more about RunSafe Identify.

RunSafe Delivers LynxOS-178 Support in Partnership with Lynx

We’re excited to share that RunSafe Protect now integrates with LynxOS-178, marking a key milestone in expanding protection for safety-critical embedded systems. The integration enables RunSafe’s runtime code protection to operate within the LynxOS-178 environment—used in aerospace, defense, and other mission-critical applications—while maintaining deterministic performance.

You can read more about this integration in our technical white paper on “Integrating RunSafe Protect with the LYNX MOSA.ic RTOS.” You can also learn more in our recent webinar on Aerospace Cybersecurity Strategy with Lynx.