The site exporter should try to actually determine package names, rather than assuming they all start with `drupal/`
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3584002. -->
Reported by: [phenaproxima](https://www.drupal.org/user/205645)
Related to !873
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Pretty much what the title says. When assembling the list of dependencies, the site exporter assumes that anything which isn't a core extension is in the <code>drupal</code> vendor namespace.</p>
<p>Not always an assumption that holds, and it both confuses people and potentially makes extra work for them.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Ask Composer to get the proper package name. This will be a performance hit, but I think it's worthwhile for the accuracy. Exporting a site is not performance-sensitive anyway.</p>
<p>If the package name can't be determined, then assume the prefix is <code>drupal</code>.</p>
issue