How to get listed

The directory's universe is exactly PackageMaven's index. If your module is in PackageMaven, it shows up here automatically the next time the pipeline runs; there's no separate submission to this site.

Steps

1. Publish on Packagist. Your module needs a public Composer package name (vendor/module-name) on Packagist.
2. Submit to PackageMaven. Use the "Submit a Module" form on package-maven.com. PackageMaven tests each module against real Magento versions and produces the quality tier, PHPStan level, and build status shown on every listing here — that's what makes compatibility data trustworthy instead of guessed from version constraints.
3. Optional: request a vendor trust file. Trusted-vendor badges, partner tiers, and editorial picks come from a human-curated overlay maintained in this repository, not from PackageMaven. Open a pull request against the GitHub repository adding or editing data/vendors/<vendor>.json. Read the trust policy first — it covers vendor identity verification, trusted-vendor eligibility, and how editorial picks are kept independent of partnership.

What the badges mean

• Trusted vendor — a sustained track record (12+ months of maintenance, no open serious warnings, responsive to issues), granted or revoked only by maintainer PR review.
• Partner tier (platinum / gold / silver / bronze) reflects a relationship with the Mage-OS organization, which may be commercial. It contributes a small, fixed, published weight to the ranking score — there is no pay-to-rank beyond that bounded weight; a commercial partnership buys a badge and a bounded ranking bump, never arbitrary placement.
• Editors’ pick is a maintainer judgment about quality or usefulness, independent of partner status. Being a partner does not make a package more likely to be picked, and picks happen for non-partner vendors routinely.

Warnings and disputes

Curators can attach warnings to a listing (info, derank, or hide severity) when there's a documented problem — for example an unmaintained package or a security advisory. Anyderank or hide warning must link public evidence, and (outside a security emergency) the vendor is notified with a response window before it merges. If you believe a warning on your package is wrong or resolved, open an issue or a counter-PR with evidence; a maintainer who wasn't involved in the original warning reviews the dispute. Full details live in the trust policy.