ibrand/laravel-express

The package has clear usage documentation, tests, and a matching repository. Its last release and repository update were in January 2019, with no recent commits and no security scanning, so maintenance and compatibility risks are substantial.

Latest v1.1

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, both from January 2019, and there have been no releases in roughly seven years. That makes compatibility and abandonment risk substantial for a Laravel integration.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the repository's last update being in January 2019.

Maintainers

Only one registry account has publish access, which creates a thin publishing base. The organization-owned repository provides some backing but does not show active release capacity.

Repo issue activity

There are no open issues or pull requests, and no recent issue or pull-request activity. This is consistent with a dormant project, though the counts alone are not severe evidence.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a meaningful hygiene gap for a package that has not been maintained recently.