Download the PHP package boesing/captainhook-vendor-resolver without Composer

On this page you can find all versions of the php package boesing/captainhook-vendor-resolver. 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?

Informations about the package captainhook-vendor-resolver

captainhook-vendor-resolver

This composer-plugin introduces a package scan for captainhook/captainhook hooks. So on every composer require, composer install or composer remove call, this plugin checks the composer.json of the installed/uninstalled package for hooks to add/remove from the captainhook.json.

NOTE: As of captainhook v5.0, you can specify a dedicated captainhook.json via --configuration. If you are using this parameter, please provide the custom captainhook.json path via captainhook-vendor-resolver.json configuration next to your composer.json.

Where is the difference to the already existing feature "includes"

As this package only parses the composer.json and automagically inserts/removes the hooks, it will provide a proper diff to your project. There is no hidden hook specified in a file outside of your project.

Your projects captainhook.json will always contain any hook which is being executed which can be easily reviewed in Pull Requests, e.g.

Example with the vendor resolver

captainhook.json

Current version of the vendor package...

vendor/package/composer.json v1.0.0

After updating the vendor package...

vendor/package/composer.json v1.0.1

diff captainhook.json

Example with includes (security implication)

captainhook.json

Current version of the vendor package...

vendor/package/captainhook.hooks.json v1.0.0

After updating the vendor package...

vendor/package/captainhook.hooks.json v1.0.1

diff captainhook.json

If you are not re-visiting your vendor packages for changes in that hook you are including, you will upload your whole project on the next git push to the attackers website.

All versions of captainhook-vendor-resolver with dependencies

PHP Build Version
Package Version
Requires php Version ^7.3
composer-plugin-api Version ^1.1
captainhook/captainhook Version ^5.0
webmozart/assert Version ^1.5
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 boesing/captainhook-vendor-resolver contains the following files

Loading the files please wait ....