Free template
Third-Party Notices Template
Provide clear license attributions and required notices for third-party components with this Third-Party Notices Template.
Downloaded 2765 times
Download template
Third-Party Notices Template
These Third-Party Notices (the “Notices”) apply to [Product Name] version [Version], released on [Release Date] by [Company Name].
1. Purpose
1.1 Purpose. These Notices provide license attributions and required disclosures for third-party software components included in the Product.
1.2 Location. These Notices are published in: ☐ NOTICE file ☐ Documentation ☐ In-app Legal screen ☐ Website ☐ Other: [Location].
2. How to Use These Notices
2.1 Component List Source. Component inventory was prepared from: ☐ SBOM ☐ Dependency scanner ☐ Manual review ☐ Other: [Source].
2.2 Completeness Note (Optional). These Notices are intended to be accurate as of the release date. If you believe a notice is missing or incorrect, contact: [Email].
2.3 Order of Notices. Components are listed: ☐ Alphabetically ☐ By product module ☐ By build artifact ☐ Other: [Method].
3. Third-Party Component Notices
3.1 Component Notice Entry (Repeat for Each Component).
Component Name: [Component Name]
Version: [Version]
License: [License Name]
Project/Homepage: [URL]
Copyright Notice(s):
[Paste required copyright lines]
Required Attribution/Notice (If Any):
[Paste required attribution language]
License Text (If Required):
[Paste license text or indicate where it is provided]
3.2 Bundled License Text Location (Optional). Full license texts are also included at: [Path/URL].
4. Additional Disclosures (Optional)
4.1 Source Code Offers (If Required). If any license requires providing source code or an offer, source code is available at: [URL], with instructions: [Instructions].
4.2 Patent Notices (If Applicable). Patent-related notices required by certain licenses are included in: [Location].
4.3 Trademarks. Third-party trademarks are the property of their respective owners.
5. Updates and Contact
5.1 Update Trigger. These Notices should be updated when:
the component list changes, or
a new product version is released.
5.2 Owner. Notices owner: [Team/Role].
5.3 Contact. Questions about these Notices can be sent to: [Email].
Signatures
By signing below, the undersigned acknowledge these Notices are intended to reflect third-party license disclosures for the identified product release as of the release date.
Prepared By: [Name]
Title/Role: [Title]
Date: [Date]
Signature: ___________________________
Approved By (Optional): [Name]
Title/Role: [Title]
Date: [Date]
Signature: ___________________________
Flash deal
Flash deal
Today
Today
No time to fill it up? Generate your custom agreement with AI Lawyer in seconds
What’s Included
Legal Research
Legal Research
Legal Research
Contract Drafting
Contract Drafting
Contract Drafting
Document Review
Document Review
Document Review
Risk Analytics
Risk Analytics
Risk Analytics
Citation Verification
Citation Verification
Citation Verification
Easy-to-understand jargon
Easy-to-understand jargon
Easy-to-understand jargon
Details
Learn more about
Third-Party Notices Template
Click below for detailed info on the template.
For quick answers, scroll below to see the FAQ.
Click below for detailed info on the template.
For quick answers, scroll below to see the FAQ.
THIRD-PARTY NOTICES TEMPLATE FAQ
What are third-party notices?
Third-party notices are a set of attributions and license disclosures that you publish when your product includes open source software or other third-party components. Many licenses require you to include copyright notices, license text, and attribution statements in a specific place (for example, a NOTICE file, documentation, or an “About” screen).
When do you need third-party notices?
You typically need them when you distribute software that includes third-party components. Some organizations also publish notices for SaaS products as a best practice, especially when customers request license transparency. If your product is shipped as an app, container, or on-prem software, notices are commonly required.
What should be included in third-party notices?
Notices usually include the product name/version, a list of included third-party components, each component’s license name, required copyright statements, required attribution language, and the license text if required. The content depends on the licenses involved, so the template is structured to help you capture each component cleanly.
Where should third-party notices be published?
Common locations include a NOTICE file bundled with the product, a section in documentation, an in-app “Legal Notices” screen, or a public webpage linked from the product. The best location is the one that reliably reaches end users and satisfies the license terms.
How do third-party notices relate to an SBOM?
An SBOM is a structured inventory of components, while third-party notices are the human-readable disclosures and license attributions. Many teams generate notices from SBOM data, but you still need to confirm each component’s license requirements before publishing.
What is AI Lawyer?
AI Lawyer is an AI-powered assistant that helps you create and customize legal and business document templates online. It guides you through key sections, suggests wording, and explains complex concepts in simple language. AI Lawyer does not replace a licensed attorney or provide legal advice, but helps you prepare better documents faster and more confidently.
Similar templates
Other templates from
Policy and Compliance Documents
Money back guarantee
Free trial
Cancel anytime
AI Lawyer protects
your rights and wallet
Money back guarantee
Free trial
Cancel anytime
AI Lawyer protects
your rights and wallet
Money back guarantee
Free trial
Cancel anytime
AI Lawyer protects
your rights and wallet
Money back guarantee
Free trial
Cancel anytime