brainlet-ali/laravel-locksmith

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last 3 months. Combined with the short release burst, this is meaningful evidence of inactive maintenance.

Project backingcaution

The package and repository are owned by the same individual account, so there is no organization backing to compensate for the thin maintainer base.

Release historycaution

There were only two releases, both published within about 9 minutes, and no later release activity across roughly 9 months. This gives limited evidence of sustained maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Repository archivedcaution

The linked repository is not archived, although its last push was at the initial release time and does not offset the lack of recent activity.