Extension review with Scrutinizer

Hi all.

I’m trying to test the code of an extension that I’m developing with Scrutinizer.
On any push I receive this warning:

I think this happens because Scrutinizer cannot check dependencies under fxp/composer-asset-plugin.
Do anyone experienced this? I’m doing something wrong?

Are you using there https://asset-packagist.org/ ?

Yes @Bizley, this is the content of its composer.json:

    "name": "letsjump/yii2-easy-ajax",
    "description": "EasyAjax are a bunch of Yii methods that minimize the amount of code you need to write to interact with Ajax CRUD, notifies, modals, tabs, pjax-reloads, form validations among others...",
    "type": "yii2-extension",
    "keywords": ["yii2", "user interface", "bootstrap", "notify", "modal", "ajax CRUD", "gii", "tabs"],
    "readme": "README.md",
    "license": "MIT",
    "authors": [
            "name": "Gianpaolo Scrigna",
            "email": "letsjump@gmail.com"
    "minimum-stability": "dev",
    "require": {
        "yiisoft/yii2": "~2.0.0",
        "bower-asset/remarkable-bootstrap-notify": "~3.1.0",
        "bower-asset/animate-css": "~3.7.0"
    "autoload": {
        "psr-4": {
            "letsjump\\easyAjax\\": "src/"
    "extra": {
        "bootstrap": "letsjump\\easyAjax\\EasyAjaxBootstrap"

I know that there are compatibility problems between Packagist and Scrutinizer.
Should I change something, for example a regression in favour of fpx/composer-asset-plugin?


How is this “yes” when I don’t see

"repositories": [
        "type": "composer",
        "url": "https://asset-packagist.org"

Yes, I probably misunderstood the composer guide:

Repositories are not resolved recursively. You can only add them to your main composer.json . Repository declarations of dependencies’ composer.json s are ignored.

It’s my first composer package and never looked at it as a main repository.
Thanks again!