Private Project License
Keep your code protected
For private projects, you have two options:
Option 1: No LICENSE File (Recommended)
Strongest protection by default
GitHub automatically shows "No license"
All rights reserved by default (no action needed)
Zero maintenance required
When to use:
- Truly private repositories
- Internal company projects
- Personal experiments
- Work-in-progress code
Option 2: Explicit LICENSE.md
Makes intent crystal clear
Professional appearance
Good for team projects
Prevents any confusion about rights
Copyright (c) 2026 [Your Name]
All rights reserved.
This software is proprietary and confidential. No license is granted to
any person or entity to use, copy, modify, distribute, or otherwise
exploit this software or its documentation.
Unauthorized use, reproduction, or distribution of this software, or any
portion of it, may result in severe civil and criminal penalties, and will
be prosecuted to the maximum extent possible under the law.When to use:
- Shared with contractors or clients
- Team repositories with external collaborators
- When you want to be extra explicit
- Commercial software projects
Pro Tips
-
For truly private repos:
No LICENSE file is the simplest and best approach. Copyright law automatically protects you.
-
For shared team repos:
Add an explicit LICENSE.md to make it clear that all rights are reserved.
-
GitHub's automatic handling:
Without a LICENSE file, GitHub automatically applies "all rights reserved" to your repository.
-
Copyright year:
Use the current year, or a range if the project spans multiple years (e.g., 2020-2026).