● Real-time Monitoring · Zero Setup

Take control of your dependencies, before the license changes

Paste your package.json and instantly discover the license status of every dependency. Stay ahead of the next Redis or Terraform surprise.

licensewatch.dev/scan

Dependency License Scan Results ✓ 32 dependencies analyzed

"dependencies": {
  "react": "^18.2.0",
  "next": "^14.0.0",
  "mongoose": "^8.0.0" ...
}

react

MIT 🟢 Safe

mongoose

MIT 🟢 Safe

some-lib

AGPL-3.0 🔴 Risk

another-pkg

LGPL-2.1 🟡 Caution

Why LicenseWatch

Discover the value behind license risks

We handle the heavy lifting — querying data, comparing rules, identifying risks — so you can focus on what matters: building your product.

Scan your project now →

🔍

Smart Detection

Automatically parse package.json and identify license types for all direct dependencies.

🛡️

99% Accuracy

Prioritize npm registry official data, combined with GitHub API for double verification.

⚠️

Real Case: Redis License Change

In March 2024, Redis switched from BSD to RSALv2, forcing thousands of commercial projects to evaluate legal risks. LicenseWatch would have alerted you on day one.

Key Features

Your open source license defense shield

📦

One-Click Parse

Paste package.json to auto-extract all dependencies — no manual sorting needed.

📊

Risk Grading

Three-color tiers make it easy to spot what needs attention at a glance.

💾

CSV Export

One-click download of the full report for archiving or sharing with your team.

⚡

Lightning Fast

Concurrent requests complete scanning of 50 dependencies in under 10 seconds.

🔓

No Registration

No account needed, no data stored. Open, use, and go.

💡

Wondering what a license means for your commercial product?

Check our license guide to quickly understand commercial restrictions for each type

Try It Now

Scan your dependencies
for license risks

Paste your package.json content to get the license status and risk level for each dependency. Export a CSV report with one click when done.

Max 50 dependencies

Analyzing...

Real Cases

Historical license changes
that caught teams off guard

These are all real license changes that forced countless teams into emergency responses.

⚡ Node.js Ecosystem

HashiCorp Terraform

📍 Infrastructure as Code

🔍 Search Engine

Elasticsearch

📍 Search & Analytics

💾 Cache Database

Redis

📍 In-Memory Database

View more cases →

★ User Review

"As an indie developer who knew nothing about license risks, this tool gave me confidence in my project's legal compliance for the first time. No more fear of stepping on landmines."

👨‍💻

Alex M.

Indie Developer · SaaS Founder

🛡️

Build with confidence,
licenses are no longer a blind spot

Join developers using LicenseWatch

FAQ

Got questions?
We've got answers

If you can't find your answer, reach out below. We offer a free one-time analysis to help assess your project's license status.

Have other questions? We're happy to help you evaluate your project's license situation with a free one-time analysis.

How does the scanning process work?

After pasting your package.json, the system parses all dependency names, then queries the npm registry public API for each package's license field, and grades risks according to preset rules. The entire process happens in your browser — your source code is never uploaded.

What dependency file types are supported?

The current version only supports package.json for the npm ecosystem. Support for go.mod and requirements.txt is under development. If you have urgent needs, let us know through feedback.

Is this tool suitable for developers new to licenses?

Absolutely. We simplified complex license judgments into three color tiers (green/yellow/red), so you can quickly spot dependencies needing attention without a legal background.

How much does it cost to get started?

The current validation version is completely free with no registration required. Just paste your package.json and use it immediately — we charge nothing.

When will continuous monitoring be available?

If the current version gets enough usage, we'll launch a monitored version with account support within 1–2 weeks, featuring weekly auto-scans and email alerts when licenses change.