Public profile

Where your profile lives

Your profile is served from the root URL /{your-slug}. If your slug is acme, your profile lives at /acme. Buyers also reach the profile when they click your name on a package detail page.

Packagento also resolves the profile when a buyer visits the URL that matches the namespace of one of your packages. So if you publish acme/premium-pro, the URL /acme returns your profile even when your marketplace slug differs from the Composer namespace.

Which fields are shown

The profile header shows:

• Display name, the human-readable name you submitted on the application form. If you have not set a name, your slug is shown in its place.
• Slug, displayed as @your-slug next to the name.
• Verified pill, shown once Packagento has approved your application. Pending vendors do not have a public profile at all, so the pill is always present on a live profile.
• Joined date, the month and year you first applied, e.g. "Joined Mar 2026".
• Website, rendered as a clickable link when you have provided one. The protocol prefix is stripped from the visible link text.
• Description, rendered as a single tagline paragraph below the header row. Plain text only; line breaks and formatting are not rendered.

Packagento does not host a logo image for vendors. The avatar tile on your profile is generated automatically from the first two alphanumeric characters of your display name (or slug if there is no name).

Below the header, your profile lists every package you have published that is visible to the public.

How to edit your profile

You edit the four profile fields (name, slug, description, website) from your vendor dashboard. Open the dashboard, click the profile edit action, update the fields, accept the current vendor terms of service, and submit.

Once your application has been approved, your slug becomes read-only. The slug is the Composer namespace for every package URL you have already published, so changing it would break existing installs. Name, website, and description remain editable for the lifetime of your account.

Edits to an approved profile are published immediately. If your status is not yet approved, edits queue the application back into pending review.

The /{your-slug}/{package} detail surface

Each of your packages has its own URL one level below your profile: /{your-slug}/{package}. So acme/premium-pro is served at /acme/premium-pro.

A specific release also has a stable URL: /{your-slug}/{package}/{version}, where {version} is a semver tag such as 1.4.2 or 2.0.0-rc1. Branch aliases like dev-master are not addressable from a URL.

The package detail page is only served when the package is approved and publicly visible. Suspended vendors, draft packages, and inclusion-only packages return a standard 404 from these URLs.

Sitemap inclusion

Approved, publicly visible packages appear in the marketplace sitemap so search engines can discover them. The sitemap entry uses the package detail URL described above and updates each time you publish a new release.

Packages set to inclusion-only visibility do not appear in the sitemap, do not have a public detail page, and do not show up on your profile. Buyers receive them only when they hold an entitling parent license; see the metapackages doc for the full picture.

Reserved slugs

A short list of slugs is reserved by the platform and cannot be claimed as your vendor slug. They overlap with built-in URLs (admin areas, checkout, the marketplace browse surface, Composer endpoints, documentation pages), and the application form rejects them with an inline error.

Reserved words include:

• Platform areas: admin, customer, checkout, sales, catalog, catalogsearch, cms, page, wishlist, contact, newsletter, review, sendfriend, multishipping, downloadable, errors.
• Static and API roots: rest, soap, graphql, static, media, pub.
• Payment integrations: paypal, braintree, stripe.
• Packagento surfaces: packages, browse, license, vendor, composer, git, quality, advisories, org, packagereport, activity.
• Documentation roots: about, privacy, terms, docs.

Slugs must also be lowercase letters, numbers, hyphens, and underscores only; the first and last character must be a letter or number. So acme, acme-tools, run_as_root, and acme2 are fine; -acme, Acme, and acme.tools are not.