Closed GuySartorelli closed 2 years ago
Scrutinizer failed because the composer1 cache hasn't got the new package yet (though why scrutinizer is using composer1 I couldn't tell you). Should be visible to composer1 in a day or so.
Scrutinizer failed this time because it's trying to use PHP 5.6... someone with access and appropriate know-how will need to update the configuration for this package's scrutinizer run.
Closing this as it's not an accepted approach. Some cool Guy has created a PR in composer/composer which will add a PHP API for consuming the packagist security advisory API, so when that's merged I'll create a new PR that leverages it.
Fixes #57