yarob/laravel-expirable

The package is small and clearly licensed, with a usable README and a simple dependency set. It has no security scanning or security policy, adding transparency gaps.

Latest v1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both in March 2017, with no releases in the last 12 months and a latest release roughly nine years ago. This is strong evidence of abandonment risk for a Laravel integration package.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with no meaningful activity since March 2017. This materially increases the chance that compatibility and defects will remain unaddressed.

Project backing

The repository is owned by an individual user rather than an organization, so the single registry maintainer is consistent with the available ownership context. No organizational backing is shown to offset the inactive project.

Repo issue activity

There was no issue or pull request activity in the last month, and there are no open issues or pull requests. With the repository already inactive for years, this supports an abandonment concern rather than demonstrating active stability.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap, not evidence that the package is malicious.