Files
Modernization-Tool/PROJECT_IDENTITY.md
T
Dusk c067770961 Harden third-party licensing and provenance
Document project identity, third-party licenses, binary and asset provenance, and move SuperWoW/SuperAPI to upstream-only distribution.
2026-08-31 16:37:10 +02:00

51 lines
1.9 KiB
Markdown

# Modernization Tool project identity
## Canonical project
The canonical repository designated by the project maintainer is:
- https://github.com/Dusk-92/Modernization-Tool
Mirrors, package caches, downstream forks, repackaged executables, and modified
copies hosted elsewhere are independent unless the canonical project explicitly
states otherwise.
## Independent community project
Modernization Tool is an independent community project. It is not affiliated
with, sponsored by, approved by, or endorsed by Blizzard Entertainment.
Compatibility with World of Warcraft, Vanilla WoW 1.12-compatible clients,
Turtle WoW-like environments, or any third-party plugin, addon, patcher, or
community project does not imply affiliation, endorsement, partnership, or
ownership.
World of Warcraft, Warcraft, Blizzard Entertainment, and associated names,
marks, artwork, audio, client files, and game assets remain the property of
their respective rights holders.
## Third-party projects
Modernization Tool can download, install, configure, or in some cases bundle
third-party components. Those projects remain independent from Modernization
Tool and retain their own copyright, licensing, support, and distribution
terms.
A source link, compatibility label, credit, installer entry, or bundled fallback
does not imply that the upstream author endorses Modernization Tool.
See `THIRD_PARTY_NOTICES.md`, `Docs/BINARY_PROVENANCE.md`, and
`LICENSES/` for the current provenance and redistribution record.
## Support boundary
Dusk-92 is responsible only for Modernization Tool releases published by the
canonical repository. Upstream component authors are not responsible for this
tool, its packaging decisions, or downstream modifications.
## Historical provenance
Do not erase historical attribution, source URLs, hashes, license notices, or
provenance records when a component is updated or replaced. Update the records
instead so the repository keeps a traceable history.