- Home
- Skills
- Legal & Compliance
- License Guardian — dependency license compliance for Claude
More screenshots
Works with the AI Agents you already use
License Guardian — dependency license compliance for Claude
Catches GPL/AGPL/LGPL/MPL exposure in your dependency tree before it becomes a legal problem.
$7
License Guardian — dependency license compliance for Claude
Example session with this skill installed
Run a license audit on the current node project. We are planning to ship this as a commercial desktop application, so we need to avoid any GPL or AGPL code in the final bundle.
- Read your context and instructions
- Compiled the license guardian
I have completed the license audit for the current npm project. I scanned the node_modules directory and analyzed the results against your distribution model as a commercial desktop application.
License Audit Report
| Package | Version | License | Category | Relationship | Action Required |
|---|---|---|---|---|---|
react | 18.2.0 | MIT | Permissive | Direct | None |
lodash | 4.17.21 | MIT | Permissive | Transitive | None |
fast-glob | 3.2.11 | MIT | Permissive | Direct | None |
readline-sync | 1.4.10 | MIT | Permissive | Direct | None |
screen-capture-utility | 2.1.0 | GPL-3.0 | Strong Copyleft | Direct | Replace |
internal-logger | 1.0.4 | AGPL-3.0 | Strong Copyleft | Transitive | Review |
source-map | 0.7.3 | BSD-3-Clause | Permissive | Transitive | None |
unknown-helper | 0.0.1 | UNKNOWN | Unknown | Direct | Verify |
Findings Summary
The scan identified 142 packages in total. Most dependencies are MIT or BSD licensed and safe for your desktop application. However, two packages represent significant risk:
screen-capture-utility (GPL-3.0): As a desktop binary, shipping this package triggers the requirement to open-source your entire application. This is a blocker for your commercial release.
2.
internal-logger (AGPL-3.0): This is a transitive dependency of your debugging suite. If this code is bundled into the production build, it carries high risk.
3. unknown-helper: No license field found in package.json. This could be proprietary or unlicensed code.
Next steps
- Replace
screen-capture-utilitywith a MIT-licensed alternative likedesktop-screenshot. - Check if
internal-loggercan be moved todevDependenciesto prevent it from shipping in the desktop binary. - Manually inspect the
LICENSEfile forunknown-helperin the project root.
Connects securely to your tools. The creator never sees your data.
About this skill
Catch risky open-source licenses before they ship. License Guardian scans your installed npm or Python dependency tree, including deeply nested transitive packages, and classifies each package’s declared license. It runs entirely offline, so private codebases stay private.
The key difference: it evaluates findings in the context of your distribution model. A GPL-licensed build tool you don’t ship is different from GPL code bundled into your product. License Guardian helps separate potential non-issues from dependencies that deserve a closer look.
What's included
! npm scanner: analyze node_modules and generate a classified report ! Python scanner: scan any installed virtual environment ! Offline analysis for private and internal codebases
Not legal advice or a substitute for counsel. Just a faster way to find the license risks worth investigating in a sprawling dependency tree.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 5 days ago
- Passed all security checks, Safe to install
Requires