attribution

name	attribution
description	Use when identifying attribution requirements that apply to software products — open-source license notices, third-party asset credits, API usage attribution, font licensing, media licensing, and data source attribution. Covers what must be attributed, how, and where across different asset types and jurisdictions. USE FOR: attribution requirements, license notices, open-source attribution, Creative Commons, font licensing, image licensing, API attribution, data attribution, NOTICE files, third-party credits, attribution in UI, attribution in documentation DO NOT USE FOR: choosing open-source licenses (use open-source-licensing), IP ownership disputes (use intellectual-property), content moderation obligations (use content-moderation)
license	MIT
metadata	{"displayName":"Attribution","author":"Tyler-R-Kendrick"}
compatibility	claude, copilot, cursor
references	[{"title":"Creative Commons Licenses","url":"https://creativecommons.org/licenses/"},{"title":"Open Source Initiative (OSI) — License List","url":"https://opensource.org/licenses"},{"title":"SPDX License List","url":"https://spdx.org/licenses/"}]

Attribution

Disclaimer: This skill provides general educational information about legal topics relevant to software development. It is not legal advice. Laws vary by jurisdiction and change frequently. Always consult a qualified attorney licensed in the relevant jurisdiction before making legal decisions for your organization.

Overview

Attribution is a legal obligation that arises from many sources — open-source licenses, Creative Commons media, font licenses, API terms of service, data provider agreements, and more. Failing to provide required attribution can constitute license violation (risking license termination and copyright infringement claims), breach of contract, or regulatory non-compliance. Many companies underestimate attribution requirements because the obligation is spread across dozens of different asset types, each with its own rules.

Attribution by Asset Type

Asset Type	Common Licenses/Terms	Attribution Required	Where to Attribute
Open-source libraries	MIT, Apache 2.0, BSD, GPL, LGPL, MPL	Yes (nearly all OSS licenses)	NOTICE file, about/legal screen, documentation
Fonts	OFL (SIL Open Font License), proprietary EULA	OFL: yes; Proprietary: per EULA	Font credits page, CSS comments, documentation
Images / Icons	Creative Commons, stock photo licenses, proprietary	CC BY: yes; Stock: per license; Proprietary: per contract	Image credits, about page, metadata
Audio / Video	Creative Commons, royalty-free licenses, sync licenses	CC BY: yes; Royalty-free: per license	Credits section, end cards, metadata
Datasets	CC BY, ODC-BY, government open data licenses	CC BY/ODC-BY: yes; Some government: yes	Data source citations, documentation
APIs	Terms of service, developer agreements	Many require "powered by" branding	UI badge/logo, documentation, per ToS
Maps	Google Maps Platform, Mapbox, OpenStreetMap	Yes (all major providers)	Map overlay attribution, per ToS
AI/ML models