Package Health/defectivecode/laravel-recall

defectivecode/laravel-recall

Healthy and reasonable to depend on. It has recent releases, active repository contributors, tests, release notes, and clear project backing; the main caveats are a single registry publisher and workflows without explicit top-level token permissions.

Latest 1.0.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

100

Supply Chain

Health Score Breakdown

Lifecycle scripts

A post-autoload-dump install-time script is present, creating some supply-chain and installation complexity; no provided workflow signal shows that it is dangerous.

Maintainers

Only one account has registry publishing access, which is a mild operational concentration risk; the organization-backed repository and two active repository contributors provide some compensation.

Repo issue activity

There are two open pull requests and no issues or merged pull requests in the last month, which is a small activity concern, though recent commits and the current release provide stronger maintenance evidence.

Token permissions

Neither analyzed workflow declares top-level token permissions, leaving permissions less explicit than recommended; neither workflow requests top-level write access.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Corey McCormick

Direct Dependencies

Dependency	Last Release	Score
illuminate/cache Version ^11.0\|^12.0\|^13.0	—	—
illuminate/support Version ^11.0\|^12.0\|^13.0	—	—
illuminate/contracts Version ^11.0\|^12.0\|^13.0	—	—