Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Generated on May 18, 2024 via composer

composer/composer 2.6.6

Composer helps you declare, manage and install dependencies of PHP projects. It ensures you have the right stack everywhere.
Package summary
Share
2
issues
2
high severity
vulnerability
2
1
license
29
MIT
Package created
31 Oct 2011
Version published
8 Dec 2023
Maintainers
2
Total deps
29
Direct deps
20
License
MIT

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
29 Packages, Including:
composer/ca-bundle@1.5.0
composer/class-map-generator@1.1.1
composer/composer@2.6.6
composer/metadata-minifier@1.0.0
composer/pcre@3.1.3
composer/semver@3.4.0
composer/spdx-licenses@1.5.8
composer/xdebug-handler@3.0.5
justinrainbow/json-schema@v5.2.13
psr/container@2.0.2
psr/log@3.0.0
react/promise@v3.1.0
seld/jsonlint@1.10.2
seld/phar-utils@1.2.1
seld/signal-handler@2.0.2
symfony/console@v6.4.7
symfony/deprecation-contracts@v3.5.0
symfony/filesystem@v7.0.7
symfony/finder@v7.0.7
symfony/polyfill-ctype@v1.29.0
symfony/polyfill-intl-grapheme@v1.29.0
symfony/polyfill-intl-normalizer@v1.29.0
symfony/polyfill-mbstring@v1.29.0
symfony/polyfill-php73@v1.29.0
symfony/polyfill-php80@v1.29.0
symfony/polyfill-php81@v1.29.0
symfony/process@v7.0.7
symfony/service-contracts@v3.5.0
symfony/string@v7.0.7
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

20
All Dependencies CSV
β“˜ This is a list of composer/composer 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
composer/ca-bundle1.5.0-MIT
prod
composer/class-map-generator1.1.1-MIT
prod
composer/metadata-minifier1.0.03.6 kBMIT
prod
composer/pcre3.1.3-MIT
prod
composer/semver3.4.028.21 kBMIT
prod
composer/spdx-licenses1.5.8-MIT
prod
composer/xdebug-handler3.0.5-MIT
prod
justinrainbow/json-schemav5.2.1356.65 kBMIT
prod
psr/log3.0.06.77 kBMIT
prod dev
react/promisev3.1.0-MIT
prod
seld/jsonlint1.10.215.79 kBMIT
prod
seld/phar-utils1.2.16.02 kBMIT
prod
seld/signal-handler2.0.27.32 kBMIT
prod
symfony/consolev6.4.7-MIT
prod
symfony/filesystemv7.0.7-MIT
prod dev
symfony/finderv7.0.7-MIT
prod
symfony/polyfill-php73v1.29.04.15 kBMIT
prod
symfony/polyfill-php80v1.29.0-MIT
prod
symfony/polyfill-php81v1.29.04.96 kBMIT
prod
symfony/processv7.0.7-MIT
prod dev

Visualizations

Frequently Asked Questions

What does composer/composer do?

Composer/composer is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you. Composer is not a package manager in the same sense as Yum or Apt are, rather it deals with packages or libraries on a project basis, installing them in a directory (e.g. vendor) inside your project.

How do you use composer/composer?

Using Composer/composer is quite straightforward. To begin, you must first download and install Composer by following the official instructions. After installation, usage of composer typically involves creating and modifying a composer.json file in your project root, which defines your project dependencies. Here's a basic example of a composer.json file:

{
    "require": {
        "vendor/package-name": "^1.0"
    }
}

On your command line, you would then navigate to your project's root directory (the directory containing composer.json), and run the install command:

composer install

This would fetch the specified package and install it in the project's vendor directory, along with any of the package's dependencies.

Also, if you want to update or add more dependencies, you would simply modify your composer.json file (or use the require command), and then run:

composer update

Where are the composer/composer docs?

Comprehensive documentation for Composer/composer can be found on the Composer official website. The documentation covers everything from getting started with installation and basic usage, to a full reference of commands and their options. For more in-depth understanding on how Composer works, you can explore the articles and tutorials available in the Composer documentation, which is accessible via the following link: https://getcomposer.org/doc/.