---
title: "Open source licence compliance review checklist (technology transactions and product releases)"
url: "https://ailawframework.com/precedents/technology-media-and-telecommunications-it-contracts/open-source-licence-compliance-review-checklist"
type: "precedent"
site: "AI Law Framework"
id: "a24-open-source-licence-compliance-review-checklist"
area_id: "A24"
kind: "checklist"
ai_level: "yellow"
version: 1
task_ids: ["A24-T1-R5"]
law_stated_as_at: "2026-10-18"
---

# Open source licence compliance review checklist (technology transactions and product releases)

> A checklist for reviewing open source use in a codebase for a sale, investment, licence-out or product release: inventory, licence classification, distribution and network-use triggers, notice and source obligations,…

Canonical page: https://ailawframework.com/precedents/technology-media-and-telecommunications-it-contracts/open-source-licence-compliance-review-checklist  
Law stated as at: 2026-10-18

Site index for agents: https://ailawframework.com/llms.txt

A checklist for reviewing open source use in a codebase for a sale, investment, licence-out or product release: inventory, licence classification, distribution and network-use triggers, notice and source obligations, licence conflicts, AI-generated code and remediation.

## Key facts

- Kind: Checklist. Steps or checks to work through and tick off.
- Practice area: [Technology, Media & Telecommunications / IT Contracts](https://ailawframework.com/precedents/technology-media-and-telecommunications-it-contracts.md)
- Jurisdictions: Australia, International / cross-border
- AI level: Yellow. AI can help in set ways. A lawyer checks specific points before use.
- Law stated as at: 2026-10-18
- Status: Maintained. Checked on 2026-10-18 against the 2 authorities it cites, for Australia and International / cross-border.

## When to use it

Use in technology due diligence, before distributing software or offering it as a service, and when a customer contract warrants open source compliance. Run it on an actual scan of the codebase, not a supplier’s summary.

## Used for these tasks

- [Build an open-source and contractor-IP issues table for a technology deal](https://ailawframework.com/practice/technology-media-and-telecommunications-it-contracts.md#A24-T1-R5)

## How AI may be used

AI may run and summarise the component scan and draft the issues table, but the lawyer classifies the licence obligations for the client’s actual distribution model and decides remediation.

**AI may:**

- Summarise a software composition analysis report into the inventory table with component, version, licence and how it is used
- Flag licences with source-disclosure, network-use or attribution obligations for review
- Draft the issues table and a remediation list for the engineering team

**AI must not:**

- Must not decide whether a licence obligation is triggered by the client’s distribution or hosting model
- Must not upload proprietary source code to a tool that retains or trains on it
- Must not treat a component’s licence as known without the licence text or SPDX identifier from the scan

**The lawyer checks:**

- The inventory comes from a current scan and covers dependencies, containers and copied snippets
- Each copyleft or network-use licence has been assessed against how the software is distributed or offered as a service
- Notice, attribution and source-offer obligations are met in the release package
- Ownership of non-open-source code written by contractors or contributors is supported by signed assignments (s 196(3))

## Authorities

- [Copyright Act 1968 (Cth) s 196(1) and (4) (copyright is personal property; a licence granted by the owner binds successors in title)](https://classic.austlii.edu.au/au/legis/cth/consol_act/ca1968133/s196.html)
- [Copyright Act 1968 (Cth) s 196(3) (assignment of copyright must be in writing signed by the assignor; relevant to contributor and contractor code)](https://classic.austlii.edu.au/au/legis/cth/consol_act/ca1968133/s196.html)

## Full text and drafting notes

The full text and the drafting notes are not part of this public page. Signed-in firm accounts can read them at https://ailawframework.com/precedents/technology-media-and-telecommunications-it-contracts/open-source-licence-compliance-review-checklist and through the signed-in MCP connector https://ailawframework.com/mcp/firm.

*Practice guidance for planning and review. Confirm current primary sources and the requirements of the actual matter. This is general information, not legal advice.*