Skip to main content
FOSSA Logo

Introducing Extended C/C++ Security and Compliance Management in FOSSA

· 5 min read·Andy Drukarev
Introducing Extended C/C++ Security and Compliance Management in FOSSA

Traditional SCA tools rely on manifest-based scanning, and that approach tends to break down in C/C++. The ecosystem has no universally adopted package manager, and engineers bring C/C++ code into their projects in many different ways.

At the same time, the organizations that rely most on C/C++ also tend to be among the most regulated. For them, an inaccurate component inventory can have significant complications when it comes to regulations like the CRA and the FDA cybersecurity rules.

Those two realities are why FOSSA’s product and engineering teams have invested heavily in security and compliance coverage for the full C/C++ ecosystem, from copy-pasted or AI-generated snippets to compiled binaries and everything in between. Today we’re announcing the general availability of the industry’s most complete solution for C/C++ security and compliance, with support for:

  • Vendored code (copy-pasted files and folders)
  • Code snippets
  • Binaries
  • Conan packages
  • Yocto packages
  • Buildroot packages

FOSSA pairs these detection capabilities with trusted workflows for open source license compliance, regulatory compliance, SBOM management, and vulnerability management. Together, they give customers one place to manage SBOMs, license compliance, and security across their C/C++ code.

Why C/C++ Needs Comprehensive Coverage

Many of our customers build automotive systems, medical devices, industrial controllers, and other embedded devices. These teams face heavy regulatory and security scrutiny, including UNECE R155 and ISO/SAE 21434 in automotive, FDA SBOM requirements for medical devices, and the EU Cyber Resilience Act for nearly any connected product sold in Europe. A single missed dependency can mean an undisclosed vulnerability or an inaccurate SBOM handed to a regulator. This can lead to product delays and/or rework; regulations like the CRA and FDA require accurate SBOMs as a prerequisite for bringing products to market.

Manifest-based SCA tools often can’t produce the complete dependency inventory that these compliance and security activities depend on. Those tools only see what a package manager has declared, and much of the open source in C/C++ projects never passes through one: it gets vendored into the repo, pasted in as snippets, compiled in through the build system, or delivered as prebuilt binaries from suppliers.

Vendored Dependencies

Our newest category of C/C++ support covers vendored dependencies. These are open source libraries that teams copy directly into their repository, often into a third_party/ folder, instead of pulling them in through a package manager. Vendored dependencies have no manifest, are rarely updated, and are often modified; they’re both easy to miss and also particularly important from a license compliance standpoint (because of the code modifications, which can trigger additional obligations).

Vendetta (the name of our vendored dependency scanner) runs as part of a standard scan (fossa analyze --x-vendetta). It fingerprints the files in your project and sends only those fingerprints to FOSSA, never your source code. It then matches the fingerprints against our knowledge base. An inference algorithm turns the file-level matches into a clean list of packages and versions. Those results flow into FOSSA’s license policies, vulnerability scanning, and SBOMs. Results are cached, so repeat scans in CI stay fast.

Package Manager and Build System Integrations

We’re also expanding support for package managers and build systems that are common in C/C++:

  • Conan: Conan is a package manager, so your dependencies are declared in a manifest. A standard FOSSA scan finds your conanfile.py or conanfile.txt and reports both direct and transitive dependencies. Add a conan.lock file to get the exact versions you build with.
  • Yocto: Yocto builds a full Linux image from source, and what ships depends on your layers, recipes, and build configuration. No manifest tells you that ahead of time, so FOSSA runs inside the build, analyzes the packages that land in your image, and can fail the build if the image violates your FOSSA policy.
  • Buildroot (coming soon): Buildroot also assembles the image at build time, but for smaller embedded systems. FOSSA will use the same build-integrated approach here.

Snippet Detection

FOSSA Snippet Scanning finds open source code that has been copied into first-party files, whether a developer pasted it from a source like GitHub or an AI coding assistant generated it. Most scans finish in under five minutes, and we’ve built functionality (such as a ranking algorithm that surfaces the most relevant matches first, optional auto-reject thresholds, and package groupings) to reduce noise and false positives often associated with snippet detection. Additionally, customers have the ability to exclude specific repos, which is useful when an organization has its own OSS repos that they do not want to have matches found against.

Snippets matter in C/C++ for the same reason vendored dependencies do: copied code has no manifest, so manifest-based tools can’t see it. AI coding assistants add one more way for that code to enter a codebase.

Binary Scanning

FOSSA Binary Composition Analysis identifies the open source inside firmware, executables, installers, and other compiled files. That includes supplier components that ship without source. It applies the same license policies and vulnerability workflows as source scanning, and it produces SBOMs and attribution notices for binaries.

Why Teams Choose FOSSA for C/C++

FOSSA is one of only a few tools that offer truly comprehensive C/C++ security and compliance coverage. That coverage also feeds directly into the license and security policy workflows and the SBOM and attribution reporting that enterprise legal, security, and engineering teams already rely on. The result is a trusted system of record that can stand up to an FDA submission, a CRA assessment, or a supplier audit.

Existing customers can contact their account team for more information about FOSSA’s extended C/C++ coverage. New to FOSSA? Schedule a demo.

Subscribe to our newsletter

Get the latest insights on open source license compliance and security delivered to your inbox.