Download the PHP package drupal/core-vendor-hardening without Composer

On this page you can find all versions of the php package drupal/core-vendor-hardening. 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 core-vendor-hardening

The Drupal Vendor Hardening Composer Plugin

Thanks for using this Drupal component.

You can participate in its development on Drupal.org, through our issue system: https://www.drupal.org/project/issues/drupal

You can get the full Drupal repo here: https://www.drupal.org/project/drupal/git-instructions

You can browse the full Drupal repo here: https://git.drupalcode.org/project/drupal

What does it do?

This Composer plugin does two things:

1) It removes extraneous directories from the project's vendor directory. They're typically directories which might contain executable files, such as test directories.

This sort of processing is required for projects that have a vendor directory inside the HTTP server docroot. This is a common layout for Drupal.

By default, the plugin knows how to clean up packages for Drupal core, so you can require drupal/core-vendor-hardening in your project and the rest will happen automatically.

The plugin can also be configured to clean up additional packages using the project's composer.json extra field.

This plugin can also clean up packages that were installed outside of the vendor directory, using composer/installers. This allows users to configure the plugin to clean up, for instance, Drupal extensions and Drupal core.

2) The plugin also adds .htaccess file to the root of the project's vendor directory. The file will perform due diligence to keep the web server from serving file from within the vendor directory.

How do I set it up?

Require this Composer plugin into your project:

composer require drupal/core-vendor-hardening

When you install or update, this plugin will look through each package and remove directories it knows about.

You can see the list of default package cleanups for this plugin in Config.php. If you discover that this list needs updating, file an issue about it: https://www.drupal.org/project/issues/drupal

In addition to the default list of packages, you can configure the plugin using the root package's composer.json extra field, like this:

"extra": {
  "drupal-core-vendor-hardening": {
    "vendor/package": ["test", "documentation"]
  }
}

The above code will tell the plugin to remove the test/ and documentation/ directories from the 'vendor/package' package when it is installed or updated.

For packages installed outside of the vendor directory, such as those installed by composer/installers, the paths to remove should be relative to the package base. As an example, a Drupal module package named drupal/module_name might be installed by composer/installers to web/modules/contrib/module_name/. Cleanup paths specified for this package might look like this:

"extra": {
  "drupal-core-vendor-hardening": {
    "drupal/module_name": ["tests", "src/Tests"]
  }
}

This would then cause the plugin to try and remove web/modules/contrib/module_name/tests and web/modules/contrib/module_name/src/Tests.


All versions of core-vendor-hardening with dependencies

PHP Build Version
Package Version
Requires php Version >=7.3.0
composer-plugin-api Version ^2
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 drupal/core-vendor-hardening contains the following files

Loading the files please wait ....