Download the PHP package designsecurity/progpilot without Composer
On this page you can find all versions of the php package designsecurity/progpilot. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download designsecurity/progpilot
More information about designsecurity/progpilot
Files in designsecurity/progpilot
Package progpilot
Short Description A Static Analyser for security
License MIT
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 progpilot
progpilot
A static application security testing (SAST) for PHP
Installation
Option 1: use standalone phar
- Download the latest phar archive from the releases page.
- Place the file somewhere in your path and make it executable:
Option 2: build phar from source code
phar-composer.phar should be located in a directory listed in the $PATH environment variable before starting the build:
The resulting phar archive will be located in the builds folder at the root of this project.
Option 3: use composer
Use Composer to install progpilot:
Configuration
Use a yaml configuration file (look at taint configuration data.
Usage
CLI example
The progpilot command takes as arguments the path to the files and folders to be analyzed and optionally a configuration file:
If you installed it with composer, the program will be located at vendor/bin/progpilot.
Library example
It is also possible to use progpilot inside PHP code. For more information look at the API documentation.
Use this code to analyze source_code1.php:
When source_code1.php contains this code:
The simplified output will be:
All files (composer.json, example1.php, source_code1.php) used in this example are in the projects/example folder. For more examples look also at this page.
Specify an analysis
It is strongly recommended to customize the taint analysis configuration (the definitions of sinks, sources, sanitizers and validators) according to the context of the application to be analyzed. In the following specification, superglobals variables _GET, _POST or _COOKIE are defined as untrusted and also the return of the shell_exec() function:
See available settings in the corresponding chapter about specifying an analysis.
Custom rules can be created too, see the corresponding chapter about custom rules.
Development
Learn more about the development of Progpilot.
Faq
Here
All versions of progpilot with dependencies
ircmaxell/php-cfg Version ^0.7.0
symfony/yaml Version ^5.4.17
symfony/console Version ^5.4.17
myclabs/deep-copy Version ^1.11.0