Jordi Boggiano

I definitely see the value in this, but I am not 100% what the consequences are in terms of getting this new conflict data to users. I think it should...

I can confirm https://packagist.org/p/akamai-open/edgegrid-client$447ea167fd0153f6ba6a6f8c05eddff6b8e09a7e8f5c957820dc9accb7296eb1.json is 404 right now, but it seems like it's having issues with one of our origin servers returning 404s for these /p/ files, I just don't...

Closing here.. I think I have found the root cause but it doesn't really matter as we are shutting down v1 metadata access next Monday anyway.

This was all quickly glued together PoC code. Good to see more extensions coming, so I guess it's time to clean this up a bit :)

Fixed the search as well to search only extensions now when on the extension page.

Took a look at this but I don't really see it sorry. This is a bit of a specific use case and I'm not sure how to best implement something...

Yeah I'm not really too keen on adding this just for the few benefits, given the little API surface we have, I'd rather keep the dependencies to a minimum as...

I don't think we really need mirroring info to be in the package.. It's still the same package after all. So adding a repository_url qualifier sounds good enough to me....

See https://github.com/composer/packagist/pull/1574 - happy to get feedback on this..

It shouldn't be your problem to fix really if there's a problem in a dependency, and often these warnings are not actual problems in reality so it makes no sense...