Unity
Third‑Party Notices & Credits: License Compliance for Unity
$39.99
Price history
Recorded standalone sale prices and the latest available store price, in USD. Historical dots use the sale start date and its recorded offer price. Prices can change during a sale; this is not a daily price log. Bundle prices and upcoming offers are excluded. History covers up to the 100 most recent recorded offers.
Lowest recorded standalone price in this history: $39.99. The latest store price is $39.99, matching the lowest recorded price shown here.
View 1 recorded price
| Sale start / price check | Price | Observation |
|---|---|---|
| $39.99 | Latest store price |
About Third‑Party Notices & Credits: License Compliance for Unity
- Tools, Systems & Learning > Development Tools & Automation
🔍 What this tool does
Generate release‑ready third‑party compliance files directly from your Unity project:
• THIRD_PARTY_NOTICES.txt
• CREDITS.md
• compliance-manifest.json
It scans your project, collects license evidence, and produces deterministic outputs you can commit to version control.
✅ Why it exists
Release‑time compliance work is usually a scramble: “what third‑party did we ship, what are the license obligations, and where are the notices/credits?”
Third‑Party Notices & Credits: License Compliance for Unity makes this a repeatable workflow inside the Unity Editor:
• Find third‑party components
• Make UNKNOWN items visible (so nothing is silently assumed)
• Export shippable files without external services
🔁 Simple workflow
1. Scan your project for third‑party components
2. Review anything marked UNKNOWN (with evidence shown)
3. Export deterministic, release‑ready files
🛡️ Designed for accuracy, not guesses
Licenses are only assigned when they can be identified with confidence. Anything uncertain is explicitly marked UNKNOWN, forcing a conscious review instead of silently introducing risk. All processing runs locally and works offline.
📦 Built for real Unity projects
Supports Unity Package Manager dependencies, Asset Store imports, embedded folders, native plugins, and copied utilities. Outputs are stable and diff‑friendly, so version control only changes when something actually changes.
🚦 Optional build-time enforcement
Enable warnings or fail builds when:
• UNKNOWN licenses exist
• Required attribution fields are missing
• Risky restrictions are detected (ex: non‑commercial, no‑derivatives, strong copyleft flags)
🏠 Homepage: See features, outputs, and what it scans.
📘 Documentation: Read setup, workflow, and export details.
🧰 Support: Get help, report issues, and ask questions.
🧩 Compatibility
Built and validated in Unity 6000.3 on Windows and Apple Silicon macOS.
Editor-only extension with zero runtime footprint, no impact on build size, and compatible with all Unity target platforms.
Verified to function correctly in Unity 2021.
❓FAQ
Q: Will it spam Git diffs?
A: No. Outputs are deterministic and avoid timestamp-only rewrites, so diffs usually reflect real dependency or attribution changes.
Q: Will it break my builds?
A: Build enforcement is configurable (warn vs fail), so you can ramp up gradually instead of hard-blocking CI on day one.
Q: What about .unitypackage imports?
A: It can detect out-of-scope imports, prompt to move them into your scan root, and optionally apply a Unity Asset Store EULA license profile when you provide a source URL.
Q: Do I need license expertise?
A: Nope. It surfaces UNKNOWN licenses and missing required attribution fields in the editor, so you focus on filling the specific gaps per component.
⚠️ Important note
This tool does not provide legal advice or guarantee compliance. It exists to surface obligations early, make them reviewable, and reduce human error before shipping.
Generate release‑ready third‑party compliance files directly from your Unity project:
• THIRD_PARTY_NOTICES.txt
• CREDITS.md
• compliance-manifest.json
It scans your project, collects license evidence, and produces deterministic outputs you can commit to version control.
✅ Why it exists
Release‑time compliance work is usually a scramble: “what third‑party did we ship, what are the license obligations, and where are the notices/credits?”
Third‑Party Notices & Credits: License Compliance for Unity makes this a repeatable workflow inside the Unity Editor:
• Find third‑party components
• Make UNKNOWN items visible (so nothing is silently assumed)
• Export shippable files without external services
🔁 Simple workflow
1. Scan your project for third‑party components
2. Review anything marked UNKNOWN (with evidence shown)
3. Export deterministic, release‑ready files
🛡️ Designed for accuracy, not guesses
Licenses are only assigned when they can be identified with confidence. Anything uncertain is explicitly marked UNKNOWN, forcing a conscious review instead of silently introducing risk. All processing runs locally and works offline.
📦 Built for real Unity projects
Supports Unity Package Manager dependencies, Asset Store imports, embedded folders, native plugins, and copied utilities. Outputs are stable and diff‑friendly, so version control only changes when something actually changes.
🚦 Optional build-time enforcement
Enable warnings or fail builds when:
• UNKNOWN licenses exist
• Required attribution fields are missing
• Risky restrictions are detected (ex: non‑commercial, no‑derivatives, strong copyleft flags)
🏠 Homepage: See features, outputs, and what it scans.
📘 Documentation: Read setup, workflow, and export details.
🧰 Support: Get help, report issues, and ask questions.
🧩 Compatibility
Built and validated in Unity 6000.3 on Windows and Apple Silicon macOS.
Editor-only extension with zero runtime footprint, no impact on build size, and compatible with all Unity target platforms.
Verified to function correctly in Unity 2021.
❓FAQ
Q: Will it spam Git diffs?
A: No. Outputs are deterministic and avoid timestamp-only rewrites, so diffs usually reflect real dependency or attribution changes.
Q: Will it break my builds?
A: Build enforcement is configurable (warn vs fail), so you can ramp up gradually instead of hard-blocking CI on day one.
Q: What about .unitypackage imports?
A: It can detect out-of-scope imports, prompt to move them into your scan root, and optionally apply a Unity Asset Store EULA license profile when you provide a source URL.
Q: Do I need license expertise?
A: Nope. It surfaces UNKNOWN licenses and missing required attribution fields in the editor, so you focus on filling the specific gaps per component.
⚠️ Important note
This tool does not provide legal advice or guarantee compliance. It exists to surface obligations early, make them reviewable, and reduce human error before shipping.