wip-license-hook

To prevent dependency license changes, you can use a license compliance tool that maintains a license ledger to track dependency licenses at adoption and blocks upstream merges if the license changes. This safeguards your project from unexpected legal issues.

You can check open-source license compliance by initializing a license ledger for your project. The system scans dependencies daily, supports npm, pip, cargo, and Go modules, and works offline using cached data and local fingerprinting.

Yes, this dependency license scanner works offline by leveraging cached data and local fingerprinting. This allows you to perform daily dependency scans and maintain license compliance without requiring a continuous network connection.

The best way to block upstream merges when a dependency license changes is using a git hook that acts as a hard gate. It compares the current license against the license ledger, automatically preventing merges if restrictive terms are detected.

You can generate a compliance dashboard by initializing the license ledger with a simple command. The tool automatically creates a public-facing dashboard that proves your project's license health and tracks all dependency licenses.

You need a license ledger when integrating open-source libraries to ensure their licenses remain permissive. It tracks the exact license of every dependency at adoption, preventing situations where a critical dependency suddenly becomes proprietary or restrictive.