reference appendices

Package Publishing Checklist

A publishable Composer package needs accurate metadata, a stable public namespace, tests, licensing, versioning discipline, and documentation that explains installation and supported runtimes.

Use This Reference When

  • Preparing an internal shared library.
  • Publishing to a Composer repository.
  • Reviewing whether a package boundary is worth maintaining.

Minimum Package Review

composer.json validates
namespace and autoload mapping are stable
PHP and extension constraints are accurate
tests pass from a clean install
license and README are present
release tag follows the versioning policy

Packages create a compatibility promise. Keep the public API small and avoid extracting code merely to create another repository.

Practice

Review a Package Manifest

Inspect a Composer package manifest and list missing metadata, platform constraints, or autoload checks before release.

Show solution

Run composer validate --strict, install from a clean checkout, check autoloading, and verify declared PHP and extension requirements against the actual code.