Yes, that's all logical. But it completely breaks the approach with promotion. I can't promote a package that doesn't exist.

Why doesn't proget cache the metadata of a package without zip?

Hello.
I keep trying to use composer feed in a real project.
There are packages with the metapackage type in composer. If you install such a package from a feed that has a connector on packagest.org, then such a package is not saved in proget as a local package. There is no corresponding folder in vendors, although it is in composer.lock.

For example:

composer reinstall -vvv --prefer-dist --no-scripts symfony/polyfill-php70

But if you try to download the zip of such a package directly, the package appears.

I think this is a mistake. All packages that are in composer.lock must be stored in proget.

Thank you.