magpie-license-compliance-audit

Audit repository license compliance for LICENSE, NOTICE, and SPDX headers.

79|76|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/apache/magpie --skill magpie-license-compliance-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magpie-license-compliance-audit
Source: https://github.com/apache/magpie/tree/main/skills/license-compliance-audit
Command: npx skills add https://github.com/apache/magpie --skill magpie-license-compliance-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for maintaining license compliance in repositories by auditing the presence and correctness of license files, NOTICE files, and source file headers.

Core Features & Use Cases

  • Read-only Audit: Inspects repositories for license compliance without modifying files.
  • Compliance Report: Generates a detailed report on license compliance issues.
  • Use Case: Before releasing a project, use this Skill to ensure all necessary license files and headers are present and correct.

Quick Start

Run the 'license-compliance-audit' skill with the repository URL: license-compliance-audit --repo owner/repo

Frequently Asked Questions about magpie-license-compliance-audit

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

FAQPage Schema
How do I audit a repository for license compliance and SPDX headers?

You can automate a repository license compliance audit by running a script that checks for the presence and correctness of LICENSE files, NOTICE files, and source file SPDX headers, generating a detailed report of any issues found.

What does a license compliance audit check for in a repository?

A repository license compliance audit inspects for the presence and correctness of LICENSE and NOTICE files, and verifies that source files contain appropriate SPDX headers, operating in read-only mode without modifying the repository.

Will running a repository license audit modify my source files?

No, a repository license audit operates in a read-only mode, inspecting for license compliance issues and reporting findings without modifying any source files or other repository contents.

When do I need to run a license compliance audit on my codebase?

You should run a license compliance audit before releasing a project to ensure all necessary LICENSE files, NOTICE files, and source file SPDX headers are present and correct, preventing potential legal issues.

Can I check for NOTICE file correctness automatically in a repository?

Yes, you can automatically check NOTICE file correctness by running an automated license compliance audit script that inspects the repository and reports on the presence and correctness of NOTICE files alongside LICENSE files and SPDX headers.