Official Publication Policy

Publication, Distribution & Verification Statement

This statement explains how official ZAMPP releases and project information are published, how third-party coverage and redistribution should be identified, how users can verify official project sources, and how the ZAMPP project name and identity may not be used to create a false impression of affiliation or approval.

Media Distribution

News sites, software directories, mirrors, video creators, bloggers, documentation sites, and other media may independently discuss or report on ZAMPP. Such coverage is welcome when it accurately identifies itself as independent and does not imply an official relationship with the ZAMPP project.

Third-party redistribution remains subject to applicable software licenses and law. A mirror, archive, repackaged build, or independently distributed copy must not be represented as an official ZAMPP release unless it is specifically authorized and identified as such by ZAMPP.org.

Verification

Users should verify ZAMPP downloads, releases, project announcements, and support channels against information published through official ZAMPP-controlled sources.

  • Confirm that the release or source is linked from zampp.org.
  • Use the official ZAMPP GitHub organization and repositories identified by ZAMPP.org.
  • Verify published SHA-256 checksums when checksum information is provided.
  • Do not assume that a matching project name or filename establishes authenticity.

zampp.org Official ZAMPP GitHub

Independent Coverage

Independent reviews, tutorials, comparisons, compatibility notes, news reporting, commentary, videos, and community discussion do not require ZAMPP endorsement simply to refer to the project accurately. They should, however, remain clearly distinguishable from official ZAMPP publications.

Independent publishers must not state or imply that they speak for ZAMPP, operate an official ZAMPP service, distribute an official ZAMPP edition, or have project authorization when no such relationship exists.

ZAMPP Name & Project Identity

The ZAMPP project name, original ZAMPP branding, logos, project presentation, and official distribution identity are proprietary identifiers of the ZAMPP project. All rights in those original project identifiers are reserved to the extent provided by applicable law.

No permission is granted by ZAMPP.org to use the ZAMPP name, logo, branding, or substantially similar project identity in a manner that falsely suggests that a third-party product, repository, operating-system edition, distribution, service, website, or organization is an official ZAMPP release or is affiliated with, authorized by, sponsored by, maintained by, or endorsed by the ZAMPP project.

Legitimate factual references to ZAMPP for commentary, compatibility information, reviews, reporting, and identification should clearly preserve the distinction between the independent source and the official ZAMPP project.

Third-Party Repositories & Unofficial Releases

ZAMPP.org is aware of at least one third-party GitHub repository using the ZAMPP name in connection with a macOS release. That repository and its macOS distribution are not affiliated with, authorized by, endorsed by, sponsored by, maintained by, or distributed by ZAMPP.org or the official ZAMPP project.

The use of the ZAMPP name in a repository title, package name, operating-system release, project description, or download does not establish an official relationship with ZAMPP.org. Unless ZAMPP.org specifically identifies a project or release as official, users should treat it as independent and unaffiliated.

Authenticity notice

If a project, repository, download, account, or distribution uses the ZAMPP name but is not identified through ZAMPP.org as an official source, do not assume that it is an official ZAMPP release or that it has been reviewed, approved, supported, or distributed by the ZAMPP project.

Official Source

Verify official ZAMPP information at ZAMPP.org.

For additional project identity, legal, redistribution, and third-party affiliation information, see the Legal & Official Project Notice.