Individual skill

licence-notice-auditor

Use when asked to check a project's licences, audit dependencies before open-sourcing or selling, write a NOTICE file, find licence conflicts, or check whether bundled fonts, images or datasets can be shipped. Produces an inventory of code, data and media dependencies with their licences, flags for conflicts and unclear ownership, and a draft NOTICE.md, with a clear statement that the output is not legal advice.

plugins/pm-oss-launch/skills/licence-notice-auditor/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Licence and Notice Auditor

Before a project is open-sourced, sold or bundled into something else, someone has to know what is inside it and on what terms. The risks are rarely in the main dependencies: they hide in a copied snippet, a bundled font, a dataset scraped years ago, or a screenshot in the docs. This skill inventories everything the project ships, flags conflicts and unclear ownership, and drafts the NOTICE file.

**This output is not legal advice.** It is a structured inventory to take to a qualified lawyer when the stakes are real: a sale, a funding round, a commercial licence, or any conflict flagged red below.

## Required Inputs

Ask for these if not provided:
- **The project's own licence**, or the licence being considered
- **How it is distributed**: source only, binaries, a hosted service, an app store, embedded in hardware
- **Dependency manifests**: package.json, requirements.txt, go.mod, Cargo.toml, or the output of a licence tool
- **Bundled non-code assets**: fonts, icons, images, audio, video, datasets, model weights
- **Copied code**: snippets from blogs, Stack Overflow, other repos, or AI tools
Back to top