Does a Packagist page prove where Composer gets my dependency?
No. Composer uses Packagist by default, but a project can configure other repositories. A public Packagist page alone does not establish where your project’s dependency resolves or which artifact you reviewed.
Composer’s repository documentation identifies the root project’s composer.json as the place additional repositories are declared. Repository declarations inside dependencies are not loaded. Check the configuration that actually governs your project, alongside the exact vendor/package name and version.
Keep the metadata source separate from the package’s source and distribution locations; the documentation explains each. If an instruction points somewhere unexpected, retain those specific references for the person reviewing dependency resolution. No installation command is needed to describe the discrepancy.
The Packagist profile guide concerns public maintainer references. ProfileTrace’s public lookup cannot inspect your private composer.json or validate the resulting artifact. Finding a familiar publishing handle does not answer the configuration question.
Results are leads, not proof of identity. ProfileTrace is not a background check and cannot be used for hiring, housing, credit or insurance decisions under the Fair Credit Reporting Act (FCRA).