FIX: Replace sensiolabs/security-checker with signify-nz/composer-security-checker #59
Conversation
|
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. |
GuySartorelli
force-pushed
the
fix/replace-sensiolabs-security-checker
branch
from
138f800
to
66ca962
Compare
…urity-checker FIX Don't instantiate security checker for /dev/tasks request. The new security checker fetches data on instantiation. There's no reason to trigger that every time a developer goes to /dev/tasks.
GuySartorelli
force-pushed
the
fix/replace-sensiolabs-security-checker
branch
from
66ca962
to
2278fd6
Compare
|
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. |
There was a problem hiding this comment.
It's a good idea, but I'm thinking it might make more sense to use the Packagist security advisory API instead. I'm thinking that's probably going to more reliable in the long term.
|
Closing this as it's not an accepted approach. |
Fixes #57