Docs & Help

Troubles during composer require

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for checkmycomposer/commands ^1.0 -> satisfiable by checkmycomposer/commands[1.0.0].
- checkmycomposer/commands 1.0.0 requires composer/composer 1.* -> no matching package found.

Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see for more details.

Read for further common problems.

Installation failed, reverting ./composer.json to its original content.

If you have a similar error when you add our package checkmycomposer/commands to your dependencies, it's very likely that you have a minimum stability set to "stable" (it's the default value if you don't specify it). This problem happens because there is not yet a stable version of Composer. Well, our package has a dependency with composer package.

At the moment, the unique solution is to set "minimum-stability" option to "alpha" and to set "prefer-stable" option to "true" in your composer.json as following:

"minimum-stability": "alpha",
"prefer-stable": true

When Composer will be available in stable version, this error shouldn't happen anymore.

Token missing

Synchronization with CheckMyComposer failed.
It seems there is no "cmc-token" parameter in your composer.json
or "cmc_token.txt" file in your project to synchronize your dependencies.
Please follow this link for more help:

As indicated, this error happens when your synchronization token is not found or incorrect.
We have 2 ways to specify your token, you will find more informations in "Getting Started" section.
You can also check if the token used is correct in "My projects" section. To do this, click on the icon corresponding to your project in "Actions" column.