license-compliance-auditor

Audit repositories for license compliance across dependencies, vendored code, fonts, assets, and snippets.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/t-step/bindle-archive --skill license-compliance-auditor-t-step
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: license-compliance-auditor
Source: https://github.com/t-step/bindle-archive/tree/main/skills/license-compliance-auditor
Command: npx skills add https://github.com/t-step/bindle-archive --skill license-compliance-auditor-t-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? License obligations hide in places a dependency manifest never shows: vendored code, fonts, images, datasets, and copied snippets. This Skill reconciles a repository's declared license against everything it actually ships, classifies risk per finding, and produces evidence-backed reports without ever making legal conclusions. ## Core Features & Use Cases - Full-surface inventory: Enumerates manifests, lockfiles, vendored directories, submodules, SPDX headers, fonts, media assets, datasets, and copied-snippet provenance markers via stdlib-only Python scripts. - Risk classification with legal boundaries: Assigns critical/high/medium/low/info risk levels using a defined taxonomy, phrases findings as likely obligation gaps, and escalates categories like cross-copyleft compatibility and linking triggers to human/legal review. - Structured reports and gated issue drafts: Normalizes findings to a stable JSON schema, renders a terminal summary plus markdown/JSON reports carrying the non-legal-advice disclaimer, and drafts grouped GitHub issues only after explicit confirmation. - Use Case: Before open-sourcing a project, run a full audit to surface a GPL dependency bundled into an MIT-declared repo, an OFL font missing its license text, and a CC-BY-NC image conflicting with commercial distribution. ## Quick Start Use the license-compliance-auditor skill to run a full license audit of this repository and write the compliance report and findings JSON.

Frequently Asked Questions about license-compliance-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a repository for license compliance?▼

Run the audit workflow: detect installed scanners with detect_tools.py, inventory the repo with inventory_repo.py, then classify each finding by risk and obligation. The skill writes license-compliance-report.md and license-compliance-findings.json to the target directory.

What license risks exist beyond the dependency manifest?▼

Vendored code, git submodules, fonts, images, audio, video, models, datasets, and copied code snippets all carry licenses that never appear in a manifest. The inventory script enumerates these surfaces, and cheatsheets cover OFL font terms and Creative Commons asset obligations.

Does the license audit require installing scanner tools?▼

No, the skill never installs anything and never touches the network. It uses whatever scanners are already present, and records missing tools as coverage gaps with install hints rather than guessing licenses from package names.

Can an automated license scan tell me if my repo is compliant?▼

No, automated detection only classifies risk and likely obligation gaps with evidence. Questions like cross-copyleft compatibility, GPL linking triggers, and trademark scope are always escalated to human or legal review, and every report carries a non-legal-advice disclaimer.

How are GitHub issues created from license findings?▼

Issue creation is never automatic. After the terminal report, the skill asks one closing question, proposes a grouped plan per finding type, and only creates issues via gh after explicit confirmation, an authenticated gh CLI, and a GitHub remote; otherwise it writes local draft files.