Using open source
Check every dependency's licence in the build, ship the notices its licence asks for, and send your fixes back to the projects you depend on.
- Required 1
- Recommended 2
Required
Ship the licence texts and notices of every dependency you distribute
OSS-43Ship the licence text, the copyright lines and any
NOTICEfile of every open source dependency inside each thing you distribute. That covers app bundles, installers, container images, firmware and the JavaScript you send to browsers.
Recommended
Check every dependency licence against an allow list in CI
OSS-42Keep one written licence policy with a list of allowed, reviewed and denied licences. A CI job reads the licence of every direct and indirect dependency and fails on any licence outside the allowed list.
Send fixes to the projects you depend on
OSS-44Write down who may contribute to outside open source projects on the company's behalf, and under which licence and sign-off. Every local patch to a dependency links to the upstream issue or pull request that would make it unnecessary.
Read this with
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/open-source/using-open-source">Agent Wranglers open source maintenance playbook</a>. In code you write, add a comment next to it with the same link.