Freedom251 › Open Source License Compliance Software
OSCake
What OSCake is
OSCake prepares open-source compliance documentation for software package collections. It uses a collection description, compliance artifacts, and results gathered by ORT to generate an OSCF.md Markdown file intended to satisfy the licenses involved. Two domain-specific languages organize the process: OSCC describes data to gather across licenses, while OSCF defines the information required for each component. OSCake interprets OSCC into OSCF, evaluates that definition with external data, filters out unnecessary artifacts for each license context, and marks missing information needed for a valid result. The project is based on Xtext and Xtend, and its repository includes example OSCC files created by ORT plus ZIP archives of additional gathered data. OSCake is free, licensed under the Eclipse Public License 2.0, and intended for on-premise deployment. Setup uses Eclipse IDE for Java and DSL Developers, or Xtext and Xtend from the Eclipse Marketplace. Configuration requires an absolute repository path for a data directory in the OSCF generator. Support is available through GitHub issues and [email protected].
Who it suits
It suits teams compiling license-aware compliance files from ORT results for software collections. On-premise deployment fits organizations managing the process in their own environment.
What it does well
- Free and on-premise
- Uses ORT-gathered results
- License-aware artifact filtering
- Flags missing compliance information
- Generates Markdown compliance output
What to know first
- Requires Eclipse-based setup
- Needs an absolute repository path
- Provided without warranties
- Requires ORT results as input
Verdict
OSCake gives teams a structured way to turn ORT data into license-appropriate compliance documentation. Its DSL-based workflow is useful when organizations can meet the Eclipse setup and repository-configuration requirements.
Facts from OSCake's own pages
- Artifact selection
- The engine filters scan results to select artifacts needed in each license context and identifies missing information. · github.com, 8 Oct 2026
- Collection language
- Its OSCC domain-specific language describes data to gather across licenses. · github.com, 8 Oct 2026
- Definition language
- Its OSCF domain-specific language defines which data must accompany each component for compliant distribution. · github.com, 8 Oct 2026
- Examples
- The repository includes example test cases consisting of OSCC files created by ORT and ZIP files containing additional ORT gathered data. · github.com, 5 Oct 2026
- Filtering and gaps
- The OSCC generator derives OSCF from collected data by omitting unnecessary artifacts and marking what is missing for a valid OSCF. · github.com, 5 Oct 2026
- Generation flow
- OSCake interprets OSCC into OSCF, then evaluates OSCF and external data to produce an OSCF.md compliance file. · github.com, 5 Oct 2026
- Inputs
- OSCake is designed to use results gathered by ORT and compile a license adequate compliance file. · github.com, 5 Oct 2026
- Integration
- The README describes using ORT-gathered results as input to OSCake. · github.com, 8 Oct 2026
- License
- The project is licensed under Eclipse Public License 2.0 and the README states the software is provided “AS IS” without warranties or conditions. · github.com, 8 Oct 2026
- License aware output
- The generated compliance file is intended to meet the requirements of the licenses involved in the package collection. · github.com, 5 Oct 2026
- Limits
- The setup instructions require configuring an absolute repository path for a data directory in the OSCF generator. · github.com, 8 Oct 2026
- Output formats
- OSCake derives an OSCF file from OSCC input and generates a Markdown compliance file from the OSCF file and external data. · github.com, 8 Oct 2026
- Purpose
- OSCake is an Xtext/Xtend-based engine that turns package collection descriptions and their compliance artifacts into an Open Source Compliance File for distribution with the package collection. · github.com, 8 Oct 2026
- Security policy
- The repository contains a SECURITY.md security policy file. · github.com, 5 Oct 2026
- Security reporting
- The security policy asks reporters not to disclose vulnerabilities in public GitHub issues and directs privacy, security concept, and media questions to [email protected]. · github.com, 8 Oct 2026
- Setup
- The documented setup uses Eclipse IDE for Java and DSL Developers, with Xtext and Xtend available through Eclipse Marketplace as an alternative installation route. · github.com, 8 Oct 2026
- Support
- The README lists GitHub issues and [email protected] as support and feedback channels. · github.com, 8 Oct 2026
- Technology
- The project describes itself as based on Xtext and Xtend, with the DSLs defined and evaluated using those technologies. · github.com, 5 Oct 2026
- Two DSLs
- OSCake defines OSCC, a weak compliance artifact language for data to gather, and OSCF, a strict language for defining data needed per component. · github.com, 5 Oct 2026
- Workflow
- OSCake takes results gathered by ORT and compiles a license-appropriate compliance file. · github.com, 8 Oct 2026