Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for manager of its

Software License Inventory Agent

A complete, version-accurate licence inventory.

Software License Inventory Agent: what goes in, what the agent does and what you get

What it does

Dependency inventories often miss licence information for indirect packages, which creates legal risk at release. Before a release, or when lockfiles change, this agent resolves the full dependency tree. It looks up licence metadata for each exact version, because licences can change between versions. When the licence for a version is missing or sources disagree, it tries another permitted lookup and then flags the package. It prepares a review report for compliance. It never draws legal conclusions. Edge case: a package was MIT licensed up to version 2 and changed licence in version 3, and the project uses version 3.1, so a name match alone would have been wrong.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Release or lockfile change 2 USES A TOOL Resolve the dependency tree 3 USES A TOOL Look up licences for exact versions 4 CHECKS THE RESULT Is the licence known for this exact version? If not: try another permitted lookup or flag it. Back tostep 3. 5 DOES Prepare the review report 6 YOU APPROVE Compliance approves the release 7 RESULT Licence inventory
Read the steps as a list
  1. Release or lockfile change
  2. Resolve the dependency tree
  3. Look up licences for exact versions
  4. Is the licence known for this exact version?If not: try another permitted lookup or flag it. Back to step 3.
  5. Prepare the review report
  6. Compliance approves the releaseThe agent waits here for your OK.
  7. Licence inventory

How it decides

It looks up unresolved versions first and flags conflicts.

  • Require an exact version match.
  • Conflicting sources are flagged, not chosen.
  • Unknown licences block the report until reviewed.

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Permitted licence lookup sources
  • Licences that always need review (default copyleft)
  • When to run (default before release and on lockfile change)
  • Who approves the release

What keeps you in control

It always asks you first

  • Legal conclusions
  • Release approval

Hard limits

  • No legal conclusions.

It stops when

  • Done: all resolved or flagged.

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensBefore the 5.4 release, the agent resolved 1,236 packages. For 1,201 the exact version had a licence. A charting package showed MIT in the registry but a different licence in its repository for version 3.1, so the check failed. A second lookup confirmed the change. The agent flagged it with both sources. Compliance reviewed the report and approved the release with a replacement planned.

More agents for manager of its