Download the PHP package terminal42/composer-lock-validator without Composer

On this page you can find all versions of the php package terminal42/composer-lock-validator. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of terminal42/composer-lock-validator

Informations about the package composer-lock-validator

Composer lock file validator

This library allows to compare a given composer.lock file against your local Composer instance.

You can use it to e.g. ensure a provided composer.lock does not contain any foreign packages (not required by your Composer instance - aka composer.json) or package URLs that have been tampered with. It also detects removed packages that should be present.

Usage:

Partial validation / validation against existing composer.lock

When you run composer update as a partial update (e.g. composer update <vendor/package> --with-dependencies), Composer will not update the composer.lock information of all the other packages. Hence, validating will probably fail because one of the other packages have experienced metadata updates in the meantime (new URL, probably abandoned, different branch-aliases etc.). In such a case, you might want to add your already existing composer.lock file as additional source of truth. Every package in the composer.lock you want to validate then has to either match the metadata of the repositories or the entry of an already existing composer.lock. Simply pass the data of the existing composer.lock as second argument:

All versions of composer-lock-validator with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
composer/composer Version ^2.8
composer/semver Version ^3.4
sebastian/diff Version ^5.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package terminal42/composer-lock-validator contains the following files

Loading the files please wait ....