Search by

thestructure / stack-check

peretzagency-creator

See when your PHP, Laravel, Symfony and Drupal versions stop getting security fixes, before a buyer, an auditor or an attacker does. Runs offline: reads composer.lock, sends nothing.

Package info

gitlab.com/thestructure/stack-check

Homepage

Issues

pkg:composer/thestructure/stack-check

Statistics

Installs: 4

Dependents: 0

Suggesters: 0

Stars: 0

v1.0.0 2026-11-20 10:05 UTC

This package is not auto-updated.

Last update: 2026-11-21 19:42:25 UTC


README

See when your PHP, Laravel, Symfony and Drupal versions stop getting security fixes, before a buyer, an auditor or an attacker does.

$ php artisan stack:check --php=8.2

Stack check by The Structure (dates as of 2026-11-20)

[HIGH]   PHP 8.2 (given with --php): security fixes until 31 December 2026 (41 days left). Bug fixes have already stopped.
         Source: https://www.php.net/supported-versions.php
[HIGH]   Laravel 12.38.1 (laravel/framework in composer.lock): security fixes until 24 February 2027 (3 months left). Bug fixes have already stopped. Runs on PHP 8.2 - 8.5.
         Source: https://laravel.com/docs/13.x/releases
  • Offline. Reads composer.lock and composer.json in your project. The dates ship with the package; it makes no network requests and sends nothing anywhere.
  • Laravel, Symfony, Drupal and plain PHP. Works as an artisan command and as vendor/bin/stack-check in any PHP project.
  • CI-ready. --fail-on=high fails the build when a version is out of security support or will be within six months.

Install

composer require --dev thestructure/stack-check

Laravel discovers the command automatically.

Use

php artisan stack:check                 # Laravel
vendor/bin/stack-check                  # any PHP project
vendor/bin/stack-check --path=../api    # another folder
OptionWhat it does
--php=8.2The PHP version production runs, if it differs from the PHP running the check.
--fail-on=highExit with code 1 when a finding reaches high, medium or low. Default none.
--jsonMachine-readable output.

Ratings: High means no security fixes any more, or six months or less left. Medium means within a year. Low means later. The command also reports a config.platform.php setting that differs from the PHP it was checked against, because a lock file built for one PHP and run on another is a finding of its own.

CI (GitHub Actions example)

- run: composer install --no-interaction
- run: vendor/bin/stack-check --php=8.4 --fail-on=high

What it checks

ComponentRead fromDates
PHP--php, or the PHP running the check8.1 to 8.5, php.net
Laravellaravel/framework in composer.lock10 to 13, Laravel support policy
Symfonysymfony/framework-bundle6.4 LTS, symfony.com/releases
Drupaldrupal/core10 and 11, Drupal release schedule

Symfony components inside a Laravel application are not reported separately: they follow the framework.

The dates live in resources/deadlines.json and come from the official schedules linked there. A new release of this package updates them, so composer update keeps the check current.

After this check, run composer audit --locked for known vulnerabilities and abandoned packages.

The full stack check

Node.js, Python, Ruby, .NET, Java, databases, Docker images, cloud runtimes and dated rules: drop your project files into the free stack check by The Structure. It reads them in your browser and uploads nothing. All the dates, with their official sources, are in the technology deadlines calendar, which you can subscribe to.

About

Made by The Structure, technical due diligence for software deals, with PERETZ, who build and upgrade Laravel products.

MIT License.