Download the PHP package padosoft/laravel-composer-security without Composer
On this page you can find all versions of the php package padosoft/laravel-composer-security. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package laravel-composer-security
LARAVEL COMPOSER SECURITY COMMAND
This is a Laravel 5.1/5.2/5.3 package that provides an artisan command for testing security vulnerabilties into your composer.lock files. Is ready and tested for php7.0 and php7.1 too.
Table of Contents
- LARAVEL COMPOSER SECURITY COMMAND
- Table of Contents
- PREREQUISITES
- INSTALL
- USAGE
- EXAMPLE:
- SCHEDULE COMMAND
- SCREENSHOOTS
- Testing
- Contributing
- Security
- API Documentation
- Credits
- About Padosoft
- License
PREREQUISITES
LARAVEL 5.1+ GUZZLE 6+
INSTALL
This package can be installed through Composer.
You must install this service provider.
You don't need to register the command in app/Console/Kernel.php, because it provides by ComposerSecurtyCheckServiceProvider register() method.
You can publish the config file of this package with this command:
The following config file will be published in config/composer-security-check.php
In config folder you can copy from .env.example the settings for yours .env file used in composer-security-check.php. If you use mathiasgrimm/laravel-env-validator in config folder you'll find and example for validate the env settings.
USAGE
When the installation is done you can easily run command to print help:
The composer-security:check command looks for every composer.lock file in the given path
and foreach composer.lock check for security issues in the project dependencies:
php composer-security:check
If you omit path argument, command look into current folder.
You can also pass the path as an argument:
php composer-security:check /path/to/my/repos
You can use in path argument as jolly character i.e. `/var/www//*/`
By default, the command displays the result in console, but you can also
send an html email by using the --mailoption:
EXAMPLE:
Here is a basic example to check composer.lock into these dir:
Here is an example to send output report to mail:
Here is an example to ignore two composer.lock vulnerabilities into two dir (if command found any vulnerabilities into these dir, write it into output but the email subject isn't set to ALERT):
SCHEDULE COMMAND
You can schedule a daily (or weekly etc..) report easly, by adding this line into schedule method in app/Console/Kernel.php :
SCREENSHOOTS
OUTPUT CONSOLE:
EMAIL VIEW WITH ALERT:
EMAIL VIEW WITH VULNERABILITY WITELISTED:
Testing
Contributing
Please see CONDUCT for details.
Security
If you discover any security related issues, please email instead of using the issue tracker.
API Documentation
Please see API documentation at https://padosoft.github.io/laravel-composer-security
Credits
About Padosoft
Padosoft is a software house based in Florence, Italy. Specialized in E-commerce and web sites.
License
The MIT License (MIT). Please see License File for more information.
All versions of laravel-composer-security with dependencies
illuminate/support Version ~5.0
illuminate/console Version ~5.0
tightenco/mailthief Version 0.*