Download the PHP package laraditz/security-scanner without Composer

On this page you can find all versions of the php package laraditz/security-scanner. 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?

Example code of laraditz/security-scanner

Informations about the package security-scanner

Laravel Security Scanner

Latest Version on Packagist Total Downloads GitHub Actions

A Laravel package that scans your application for common security vulnerabilities via a single Artisan command. It produces a color-coded terminal report and saves detailed JSON and HTML report files.

Requirements

Installation

Laravel auto-discovers the service provider. No further configuration is needed.

Usage

Basic scan

Scans your entire Laravel application rooted at base_path():

Scan a specific path

Save reports to a custom directory

Options

Option Default Description
--path base_path() Path to the Laravel application root to scan
--output storage/logs/ Directory where JSON and HTML report files are saved

What Gets Scanned

Nine independent checkers run on every scan:

Checker Severity What it detects
SqlInjectionChecker CRITICAL / HIGH Raw queries with string concatenation or variable interpolation; DB::unprepared() usage
XssChecker HIGH Unescaped {!! $var !!} Blade output without a sanitizer
MassAssignmentChecker HIGH / MEDIUM Eloquent models with $guarded = [] or no $fillable/$guarded defined
SecretsChecker CRITICAL Hardcoded credentials, API keys, Stripe keys, AWS access keys; APP_DEBUG=true in .env
FileUploadChecker CRITICAL / HIGH Files stored in public/; getClientOriginalName() usage; extension-only MIME validation
MaliciousFileChecker CRITICAL PHP files in upload directories; webshell signatures (eval(base64_decode(, system($_GET, etc.)
AuthorizationChecker HIGH Routes under /admin, /dashboard, /management without auth middleware
CsrfChecker CRITICAL / HIGH Wildcard CSRF exceptions (e.g. /api/*) in VerifyCsrfToken
RateLimitChecker HIGH Login, register, and password reset routes without throttle middleware

See docs/checkers.md for detailed descriptions, examples of vulnerable vs. safe code, and remediation advice for each checker.

Output

Terminal

Findings are printed to the console grouped by severity (CRITICAL → HIGH → MEDIUM → LOW → INFO), each with:

A summary count by severity is printed at the end.

Report files

Two files are saved after every scan:

File Description
security-scan-YYYY-MM-DD.json Machine-readable report with all findings and any checker errors
security-scan-YYYY-MM-DD.html Dark-themed HTML table report, suitable for sharing with a team

Both are saved to storage/logs/ by default (or the directory specified via --output).

Severity levels

Level Meaning
CRITICAL Actively exploitable; fix immediately
HIGH Significant risk; fix before next deployment
MEDIUM Should be addressed; risk depends on context
LOW Best-practice improvement
INFO Informational; no immediate action required

Error resilience

If a checker throws an unexpected exception while processing a file, the scanner logs the error and continues — the remaining checkers still run and their findings are still reported. Checker errors are listed in the terminal output and included in the JSON report.

CI integration

You can run the scanner in CI and fail the pipeline if any findings are returned:

Testing

Changelog

Please see CHANGELOG for more information what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Credits

License

The MIT License (MIT). Please see License File for more information.

All versions of security-scanner with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/support Version ^10.0|^11.0|^12.0
symfony/finder Version ^6.0|^7.0|^8.0
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 laraditz/security-scanner contains the following files

Loading the files please wait ...