For open source

Free hosting for
free Magento modules,
quality you can prove.

Host your free packages on the same Composer V2 endpoint that powers the paid catalog. Automated quality checks publish their results as visible badges on your listing. Merchants discover your work through the registry, not only through GitHub stars.

composer
# merchants install your free
# module the same way they install paid
composer require your-vendor/your-module

# no zip downloads, no git submodules,
# updates flow through composer update
Free hosting Pass-fail badges

Four automated checks on every release

Code style
PHPCS
Static analysis
PHPStan
Security audit
composer audit
Duplication
copy-paste

Results land on the release page within minutes of the tag push. A green badge on a free module is the trust signal merchants would otherwise have to assess by hand. See quality and review for the per-tool detail.

What you get, at no cost

Free Composer endpoint

Composer V2 endpoint with caching. Versioned downloads for every tag you push. Audit trail for every release. Buyers install as fast as they would from Packagist.

Discovery via the registry

Clean URLs at packagento.com/your-vendor/your-package. Categorisation, tags, compatibility filters built on the metadata you already declare in composer.json.

Quality badges, public

Each release shows pass or fail for the four automated checks. Merchants filter the registry by quality before clicking into a listing, so good code wins.

Verified vendor signal

Your Packagento listing links to the GitHub org or user that owns the source. Merchants see the provenance signal without having to chase repository URLs through layers of forks.

Composer install for buyers

No zip downloads, no clone-and-symlink, no git submodule. Free Packagento packages install with composer require, the same one-liner used for paid modules.

Optional path to paid

Free is free, but the door to monetisation is on the same hinges. Switch a release line to paid later without losing the existing free version or its installed base.

What we ask in return

1

A one-time package review

When you add the package: do you own the repository, is the licence clear, does the metadata read coherently. Most reviews clear within a few business days.

2

Conventional composer.json

Follow the conventions every other Packagist package follows. No new format to learn, no proprietary fields.

3

Tags drive releases

Push a semver tag, the automated checks run. There is no manual review per release, no portal flow, no zip upload.

Your public vendor profile

Every approved publisher (free or paid) gets a public profile page at packagento.com/{your-slug}. Display name, bio, homepage, repository, documentation, every package you maintain, the verified-vendor badge once your GitHub or GitLab org is linked back. Search engines index it; merchants land on it from the browse surface. See the vendor public profile docs.

  • Profile and package pages are indexable and link-friendly. Buyers who would never search Packagist still find your work through a category search.
  • Verified-vendor badge maps your slug to your GitHub or GitLab org. Identity signal without you having to write a README about it.
  • All your packages on one page. New visitors arriving for one module see the rest of the catalogue without leaving.

Activity feed for your packages

Vendor activity at packagento.com/vendor/activity shows every release, install token issued, and quality check outcome in one timeline. Free packages get the same instrumentation as paid: you see who is installing your module and how often, even though no money is changing hands. See the activity feed docs for the row format.

  • Release events show the tag pushed, the QA results, and how many installs landed on it. Easy to spot when an old tag still has traction.
  • Install events tell you which projects activated which versions. Bug reports become easier to triangulate against version share.
  • When you switch a release line to paid later, the same feed shows you the buyer events on the new versions. Same dashboard, the model under it changed.
For open source

Publish your free module.

Apply once, connect your Git provider, push a tag. Free hosting, automated quality, real merchant discovery.

Related documentation