audit-licenses

To audit open-source licenses, you run a check against project manifests to identify and summarize the licenses of direct dependencies, highlighting copyleft licenses like GPL and AGPL. It outputs a human-readable summary and a machine-readable JSON artifact for compliance tracking.

You need to check for GPL and AGPL licenses because these copyleft licenses force a project that uses them to be open-sourced under the same terms. Identifying these licenses in your dependencies ensures you understand compliance obligations before shipping.

Yes, you can check dependency licenses across npm, Python, and Go projects. The license compliance audit reads the standard project manifests for these ecosystems to detect direct dependencies and summarize their open-source licenses.

You need bash, jq, and standard project manifests to generate a license compliance report. The audit process uses these standard environment tools to read dependencies and output a JSON artifact detailing the open-source licenses.

Yes, the license audit saves a machine-readable JSON artifact so future skills can read and reason about the results. This saved artifact allows downstream automated workflows to access the dependency compliance data.