Freedom251 › Open Source License Compliance Software
Check License Compliance

What Check License Compliance is
Check License Compliance is an open-source GitHub Action for checking repository dependencies against license policies. It supports Node.js packages from NPM, Python packages from PyPI, Maven and Go. The action reads manifest files and retrieves dependency-tree details recursively through the deps.dev API, so packages do not need to be installed first. Policies can allow, forbid or warn on licenses, with configurable treatment for other or unknown licenses. Configuration can come from a YAML file, action inputs, or both, and can select or exclude dependencies and files. It runs in GitHub Actions workflows, and a composite action can post results as a pull request comment. Reports are available as text, Markdown or JSON, with details about noncompliant dependencies, installation paths and licenses. The action runs using a Docker image defined by the repository's Dockerfile. The project is licensed under Apache-2.0 and identifies Telefónica Innovación Digital as its author. The listed plan costs nothing. License expressions using AND or OR are not supported; simple SPDX identifiers, plus-ranges and exceptions are supported.
Who it suits
It suits teams that want to check repository dependency licenses in GitHub Actions, including those working with NPM, PyPI, Maven or Go projects.
What it does well
- Checks dependencies without installing them first
- Supports four package ecosystems
- Can allow, forbid or warn on licenses
- Reports results as text, Markdown or JSON
- Can comment on pull requests
What to know first
- License expressions using AND or OR are unsupported
- The listed deployment is a GitHub Action
Limits
License expressions using AND or OR are not supported. The listed plan is free and is Apache-2.0 licensed.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Check License Compliance | Apache-2.0 licensed open-source GitHub Action | Free |
As github.com lists them, read 4 Oct 2026. The maker's own page has the final word.
Getting started
- Open the project website on GitHub.
- Add the GitHub Action to a GitHub Actions workflow.
- Set configuration in a YAML file, action inputs, or both.
- Choose which dependencies and files to include or exclude.
- Set license policies and choose a report format.
Verdict
Check License Compliance offers configurable license checks within GitHub Actions, with detailed reports and pull request comments. Its unsupported AND and OR expressions are an important policy-matching limit to consider.
Questions
What does Check License Compliance cost?
The listed plan is free. The project is open source under Apache-2.0.
Which ecosystems does it check?
It checks dependencies for Node.js (NPM), Python (PyPI), Maven, and Go.
Does it require dependencies to be installed?
No. It reads manifest files and retrieves dependency tree information recursively from the deps.dev API.
Where can it run?
It is provided as a GitHub Action for GitHub Actions workflows. Its listed platforms are Linux and self-hosted, with on-premise deployment.
What reports can it produce?
Results can be reported as text, Markdown, or JSON, with details about noncompliant dependencies, installation paths, and licenses.
Which license formats are supported?
Simple SPDX identifiers, plus-ranges, and exceptions are supported. Expressions using AND or OR are not supported.
Facts from Check License Compliance's own pages
- CI integration
- The product is provided as a GitHub Action that can run in GitHub Actions workflows. · github.com, 4 Oct 2026
- Configuration
- Configuration can be supplied in a YAML file, through action inputs, or both, and supports selecting or excluding dependencies and files. · github.com, 4 Oct 2026
- Dependency lookup
- Reads manifest files and retrieves dependency tree information recursively from the deps.dev API, without requiring dependencies to be installed first. · github.com, 4 Oct 2026
- Deployment
- The GitHub Action runs using a Docker image defined by the repository's Dockerfile. · github.com, 4 Oct 2026
- License matching limit
- License expressions using AND or OR are not supported; simple SPDX identifiers, plus-ranges, and exceptions are supported. · github.com, 4 Oct 2026
- Maker
- The action identifies its author as Telefónica Innovación Digital. · github.com, 4 Oct 2026
- Open-source license
- The project is licensed under Apache-2.0. · github.com, 4 Oct 2026
- Organization location
- The Telefónica GitHub organization profile lists Spain. · github.com, 4 Oct 2026
- Policy controls
- Policies can allow, forbid, or warn on licenses, with configurable behavior for other or unknown licenses. · github.com, 4 Oct 2026
- Pull request comments
- A composite action can post check results as a comment on a pull request. · github.com, 4 Oct 2026
- Purpose
- Checks repository dependencies against allowed, forbidden, and warning license policies. · github.com, 4 Oct 2026
- Reports
- Results can be reported as text, Markdown, or JSON, including details about noncompliant dependencies, their installation paths, and licenses. · github.com, 4 Oct 2026
- Supported ecosystems
- Checks dependencies for Node.js (NPM), Python (PyPI), Maven, and Go. · github.com, 4 Oct 2026