The following table indicates which versions of Project Template are currently receiving security updates. Only actively supported versions should be used in production.
| Version | Supported |
|---|---|
| 1.6.x | ✅ |
| < 1.6 | ❌ |
This project relies on several dependencies to function. Below is a list of key dependencies and their required versions as per the composer.json file:
- PHP:
^8.3 - Laravel Framework:
^11.0 - API Ecosystem for Laravel/Dingo API:
^4.2 - Blade UI Kit (Heroicons):
^2.1 - Blade UI Kit (Icons):
^1.5 - Cleanique Coders (Laravel Action):
^2.0 - Cleanique Coders (Laravel Blacklist):
^1.1 - Cleanique Coders (Laravel Media Secure):
^2.0 - Cleanique Coders (Mail History):
^2.1 - Cleanique Coders (Traitify):
^1.0 - Diglactic (Laravel Breadcrumbs):
^9.0 - Doctrine/DBAL:
^3.5 - GuzzleHttp/Guzzle:
^7.2 - Lab404 (Laravel Impersonate):
^1.7 - Laravel Horizon:
^5.23 - Laravel Jetstream:
^5.0 - Laravel Sanctum:
^4.0 - Laravel Telescope:
^5.0 - Laravel Tinker:
^2.8 - League (Flysystem AWS S3 V3):
^3.0 - Livewire/Livewire:
^3.4 - Owen It (Laravel Auditing):
^13.1 - Predis/Predis:
^1.1 - Rappasoft (Laravel Livewire Tables):
^3.1 - Spatie (Laravel Media Library):
^11.0 - Spatie (Laravel Permission):
^6.0 - Yadahan (Laravel Authentication Log):
^1.6
- Barryvdh (Laravel Debugbar):
^3.8 - Cleanique Coders (Laravel DB Doc):
^1.1 - Driftingly (Rector Laravel):
^1.2 - FakerPHP/Faker:
^1.9.1 - FriendsOfPHP/PHP-CS-Fixer:
^3.8 - Jason McCreary (Laravel Test Assertions):
^2.4 - Larastan (PHPStan for Laravel):
^2.9 - Laravel Shift (Blueprint):
^2.10 - Laravel Pint:
^1.2 - Laravel Sail:
^1.18 - Mockery/Mockery:
^1.4.4 - Nuno Maduro (Collision):
^8.1 - Overtrue/PHPLint:
^9.4 - PestPHP/Pest:
^3.0 - PestPHP/Pest Plugin for Laravel:
^3.0 - Rector/Rector:
^1.2 - Spatie (Laravel Ignition):
^2.0
If you discover a security vulnerability in Project Template, please follow these steps to report it responsibly:
-
Do not open a public issue.
Security vulnerabilities must be reported privately to ensure they can be addressed before disclosure. -
Send an email.
Email the vulnerability details to Nasrul Hazim at nasrulhazim.m@gmail.com. -
Include the following details:
- A description of the vulnerability.
- Steps to reproduce the issue, if applicable.
- Any potential impact or exploit scenarios.
We will investigate and respond promptly. Once the vulnerability is resolved, appropriate credit will be given to the reporter if desired.
When a vulnerability is resolved, updates will be released for supported versions. Users are encouraged to stay on the latest versions to ensure they benefit from the latest security patches.