Skip to content
TrustedSkillsbeta
Back to all skills

License Compliance Auditor

Checked
jorgealves·vlatest·security·GPL-3.0

This tool automatically checks software installations against license agreements, ensuring regulatory adherence and preventing costly legal issues.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jorgealves/agent_skills --skill license-compliance-auditor -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jorgealves

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jorgealves/agent_skills at 85014ad37d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
85014ad37d
Manifest
license-compliance-auditor/SKILL.md
Scanned
2 files, 88 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

license-compliance-auditor

What it does

This skill enables AI agents to automatically scan software dependencies and identify potential licensing violations within codebases. It provides detailed reports on open-source components, highlighting specific licenses that may conflict with your organization's compliance policies or commercial distribution requirements.

When to use it

  • Before releasing a new product to ensure all third-party libraries align with your intended distribution model.
  • During internal audits to detect risky licenses like GPL in proprietary codebases before legal review.
  • When integrating new open-source packages to verify they do not introduce unexpected copyleft obligations.
  • To generate compliance documentation for security teams or external auditors requiring license inventories.

Key capabilities

  • Scans project dependencies across various package managers and language ecosystems.
  • Identifies specific licenses associated with each detected software component.
  • Flags potential conflicts between library licenses and organizational usage policies.
  • Generates structured reports summarizing compliance status and risk levels.

Example prompts

  • "Audit the current Node.js project dependencies and list any licenses that are incompatible with commercial closed-source distribution."
  • "Scan this Python repository for open-source libraries and highlight those requiring source code disclosure if distributed."
  • "Generate a summary of all third-party licenses used in this microservice architecture and flag any with restrictive clauses."

Tips & gotchas

Ensure you provide the agent with access to your dependency manifest files (e.g., package.json, requirements.txt) or repository permissions for accurate scanning. This tool identifies potential risks but should not replace formal legal counsel for final compliance decisions.