OXIESEC PANEL
- Current Dir:
/
/
usr
/
share
/
doc
/
composer
/
faqs
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
07/20/2024 06:32:22 AM
rwxr-xr-x
📄
how-do-i-install-a-package-to-a-custom-path-for-my-framework.md
1.79 KB
01/31/2018 03:28:18 PM
rw-r--r--
📄
how-to-install-composer-programmatically.md
1.38 KB
01/31/2018 03:28:18 PM
rw-r--r--
📄
how-to-install-untrusted-packages-safely.md
938 bytes
01/31/2018 03:28:18 PM
rw-r--r--
📄
should-i-commit-the-dependencies-in-my-vendor-directory.md
1.66 KB
01/31/2018 03:28:18 PM
rw-r--r--
📄
why-are-unbound-version-constraints-a-bad-idea.md
1.06 KB
01/31/2018 03:28:18 PM
rw-r--r--
📄
why-are-version-constraints-combining-comparisons-and-wildcards-a-bad-idea.md
998 bytes
01/31/2018 03:28:18 PM
rw-r--r--
📄
why-can't-composer-load-repositories-recursively.md
2.06 KB
01/31/2018 03:28:18 PM
rw-r--r--
Editing: how-to-install-untrusted-packages-safely.md
Close
# How do I install untrusted packages safely? Is it safe to run Composer as superuser or root? Certain Composer commands, including `exec`, `install`, and `update` allow third party code to execute on your system. This is from its "plugins" and "scripts" features. Plugins and scripts have full access to the user account which runs Composer. For this reason, it is strongly advised to **avoid running Composer as super-user/root**. You can disable plugins and scripts during package installation or updates with the following syntax so only Composer's code, and no third party code, will execute: ```sh composer install --no-plugins --no-scripts ... composer update --no-plugins --no-scripts ... ``` The `exec` command will always run third party code as the user which runs `composer`. In some cases, like in CI systems or such where you want to install untrusted dependencies, the safest way to do it is to run the above command.