jimhlad/leapfrog

The MIT license, readable documentation, and release notes make the package transparent to inspect. Its small dependency set and lack of install-time scripts reduce integration friction, but they do not offset the maintenance risk.

Latest 1.1.1

Packagist

12%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Using this package? Scan for Free

Health Score Breakdown

Registry deprecation

Packagist marks the entire package as abandoned, with no replacement listed. This is a severe dependency-health warning because the release is no longer presented as maintained.

Release history

The package has had no releases in the last 12 months and its latest release dates to August 2017. That long period without releases strongly indicates abandonment for a Laravel integration package.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the archived repository, this confirms that current maintenance capacity is absent.

Repository archived

The linked repository is archived and was last pushed in August 2017, so upstream changes and issue responses should not be expected.

Repo issue activity

There was no issue or pull-request activity in the last month, and no open issues or pull requests. This is consistent with an inactive project, though it is supporting evidence rather than proof by itself.