# What Is the License for the actions/checkout Repository?

> Discover the MIT License for the actions/checkout repository. Use, modify, and distribute freely in GitHub Actions workflows. Learn more about its terms.

- Repository: [GitHub Actions/checkout](https://github.com/actions/checkout)
- Tags: getting-started
- Published: 2026-07-03

---

**The actions/checkout repository is released under the MIT License, a permissive open-source license that allows free use, modification, and distribution in both open-source and proprietary GitHub Actions workflows, provided you retain the original copyright notice and license terms.**

The actions/checkout repository is the official GitHub Action used by millions of CI/CD pipelines to clone repositories into workflow environments. Understanding the license for the actions/checkout repository is essential for legal compliance when integrating this dependency into your software development lifecycle. The project is actively maintained by GitHub, Inc. and community contributors, with all source code protected under a business-friendly license that minimizes adoption barriers for enterprise teams.

## MIT License Terms and Conditions

The actions/checkout repository is governed by the MIT License, with the complete legal text residing in the repository's root [`LICENSE`](https://github.com/actions/checkout/blob/main/LICENSE) file. According to the source code, the copyright notice specifies **© 2018 GitHub, Inc. and contributors**, followed by the standard MIT permission grant statement.

This license type grants broad freedoms including the right to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software. The only substantive requirement is that you must include the original copyright notice and permission notice in all copies or substantial portions of the software.

## Compliance Requirements for Usage

While the MIT License is highly permissive, compliance involves specific obligations when redistributing the code or incorporating it into derivative works.

### Attribution Obligations

You must retain the copyright notice "© 2018 GitHub, Inc. and contributors" and the full license text when distributing the actions/checkout source code. This requirement applies if you fork the repository, bundle the `src/` directory with other tools, or modify the core logic in [`src/main.ts`](https://github.com/actions/checkout/blob/main/src/main.ts) for internal redistribution.

### Proprietary and Commercial Usage

The license explicitly permits usage in proprietary workflows. You can invoke `actions/checkout@v4` in private enterprise repositories without publishing your own source code or paying licensing fees. The MIT obligations are satisfied by the public availability of the license file; you do not need to include the license text in your own workflow YAML files unless you are physically redistributing the action's source code.

## Repository Files Covered by the License

The MIT License covers all files in the repository, including implementation logic, configuration metadata, and documentation. Key files subject to these terms include:

- **[`action.yml`](https://github.com/actions/checkout/blob/main/action.yml)**: Defines the action's inputs, outputs, and runtime environment specifications.
- **[`src/main.ts`](https://github.com/actions/checkout/blob/main/src/main.ts)**: Contains the core TypeScript implementation that executes Git checkout operations and handles authentication.
- **[`README.md`](https://github.com/actions/checkout/blob/main/README.md)**: Documentation covering usage patterns, input parameters, and configuration examples.
- **`LICENSE`**: The MIT license text governing the entire codebase.

All modifications to these files, whether to the Git logic in [`src/main.ts`](https://github.com/actions/checkout/blob/main/src/main.ts) or the interface definitions in [`action.yml`](https://github.com/actions/checkout/blob/main/action.yml), remain subject to the original license terms.

## Practical Workflow Examples

The following YAML configurations demonstrate standard usage patterns that comply with MIT License terms.

Standard CI workflow integration:

```yaml
name: CI
on: [push, pull_request]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

```

Using a specific commit reference:

```yaml
- name: Checkout a specific commit
  uses: actions/checkout@v4
  with:
    ref: ${{ github.sha }}

```

These configurations consume the action as a dependency through the GitHub Actions marketplace, which constitutes permitted use without additional attribution requirements beyond the standard marketplace display.

## Summary

- The actions/checkout repository is licensed under the **MIT License**, a permissive open-source license.
- Copyright is held by **GitHub, Inc. and contributors** (© 2018).
- You may use the action in **both open-source and proprietary workflows** without restriction.
- Redistribution of source code requires preserving the **copyright notice and license text** from the `LICENSE` file.
- Core implementation files including [`src/main.ts`](https://github.com/actions/checkout/blob/main/src/main.ts) and [`action.yml`](https://github.com/actions/checkout/blob/main/action.yml) are fully covered by these license terms.

## Frequently Asked Questions

### Is actions/checkout free to use in commercial projects?

Yes, the MIT License explicitly permits commercial use without royalty fees. You can integrate actions/checkout into private enterprise repositories and commercial CI/CD pipelines without disclosing your proprietary source code. The license only requires that you retain the copyright notice if you redistribute the action's source code itself.

### Where can I find the full license text for actions/checkout?

The complete MIT License text is located in the [`LICENSE`](https://github.com/actions/checkout/blob/main/LICENSE) file at the root of the repository. This file contains the copyright attribution to GitHub, Inc. and contributors dated 2018, along with the full permission grant that governs all repository files including [`src/main.ts`](https://github.com/actions/checkout/blob/main/src/main.ts) and [`action.yml`](https://github.com/actions/checkout/blob/main/action.yml).

### Do I need to include the MIT License notice in my GitHub Actions workflow files?

No, you do not need to include the license text in your [`.github/workflows/ci.yml`](https://github.com/actions/checkout/blob/main/.github/workflows/ci.yml) files or other workflow definitions. Referencing `uses: actions/checkout@v4` constitutes normal usage, not redistribution. The attribution requirement applies only when you distribute copies of the action's source code or create derivative works based on the repository contents.

### Can I modify the actions/checkout source code for internal use?

Yes, the MIT License grants you the right to modify, merge, and distribute the source code. If you fork the repository and modify files like [`src/main.ts`](https://github.com/actions/checkout/blob/main/src/main.ts) to implement custom checkout logic or authentication methods, you must retain the original copyright notice and include the MIT License text in your modified version. This allows you to maintain private forks while remaining compliant with the license terms.