krato/larasafe

Release historydanger

Only two releases were published, both in July 2015, with no release in more than 10 years. This is strong evidence of a potentially abandoned dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the release history showing more than a decade without updates.

Maintainerscaution

Only one registry maintainer is listed. This is a thin publishing base and increases continuity risk, especially alongside the lack of recent activity.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no provided organizational backing to offset the single-maintainer and inactivity concerns.

Repo popularitycaution

The repository has one star, one fork, and one watcher, providing little supporting evidence of active adoption or community resilience.