OSS license checking is inconsistent
Different developers use different methods for license verification, leading to oversight and incorrect judgments.
Automate OSS License Management
Easily check licenses with GitHub Actions. Reduce compliance risk and improve development efficiency.
Are you facing these challenges?
License verification per project is tedious
Manually checking licenses every time dependencies increase is time-consuming.
Aligning internal policies with OSS licenses is complex
Determining compliance with legal and regulatory requirements is complex and requires specialized knowledge.
Key Features
Automatically detect dependency licenses
Reads dependencies from lock files such as package-lock.json, pylock.toml, Gemfile.lock and automatically retrieves license information for each package. No manual checking required.
Auto-approve/reject with custom policies
Define your organization's policy (e.g., MIT and Apache-2.0 allowed, GPL-3.0 rejected) and automatically enforce consistent license checks when dependencies increase.
Seamlessly works with GitHub Actions
Add just a few lines to your workflow file to run license checks at PR or scheduled times. Easy integration into your CI/CD pipeline.
AI-driven clear license explanations
LLM explains the characteristics and considerations of each license in plain language. Make informed decisions without legal expertise.
How It Works
1. Sign up / Log in
Log in with your GitHub account and select a plan. You can start for free with the Free plan right away.
2. Get your license key
Copy the license key issued in your dashboard. You'll use this key in GitHub Actions.
3. Add to GitHub Actions workflow
Create a workflow file in .github/workflows/ and set your license key as a secret. Setup complete in minutes.
4. At PR or Scheduled Times
From now on, license checks run at Pull Request or scheduled times, with results posted as comments.
Pricing Plans
Free
Individual developers & small projects
$0/month
0 CPT/month (10 CPT initial grant)
Public repositories only
1 user
Basic license detection
GitHub Actions integration
Public repositories only
Starter
Small teams
$5-7/month
50 CPT/month
Up to 5 private repositories
Up to 3 users
All Free features
50 CPT/month
Up to 5 private repositories
Up to 3 users
Recommended
Plus
Growing teams
$15-20/month
150 CPT/month
Unlimited repositories
Up to 10 users
All Starter features
150 CPT/month
Unlimited repositories
Up to 10 users
Enterprise
Large organizations & custom requirements
Contact Us
Custom CPT allocation
Custom limits
Unlimited users
All Plus features
Custom CPT allocation
Custom repository limits
Unlimited users
Dedicated support
1 OSS license scan = 1 CPT
Unused CPT does not roll over to the next month (except Enterprise plan)
Frequently Asked Questions
Please provide your own LLM API key. We do not use your LLM in GitHub Actions.
Yes, custom policies are available. You can configure policies from the Web UI and apply them to each project.
Public repositories are free. However, if you use LLM-powered analysis, you will need to pay for LLM costs separately.
OSS Lens prioritizes user data protection. Only the repository name and URL are sent to our servers.
Yes. The Enterprise plan supports on-premise deployment. Please contact us for details.
Currently, it's GitHub Actions only, but we're considering support for other CI/CD platforms in the future.
Yes. You can change plans with one click from your dashboard. Your license key remains the same, and features are extended immediately.