rastik1584/laravel-mapycz-api

Maintainerscaution

Only one registry account can publish releases. This is a real continuity risk for a user-owned project because a single publisher provides little redundancy if maintenance stops.

Project backingcaution

The repository and registry are owned by the same individual account rather than an organization. That matches the single-maintainer profile but provides no organizational continuity buffer.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Although a release occurred recently, the lack of follow-up development lowers confidence in ongoing maintenance.

Repo popularitycaution

The repository has one star, no forks, and no watchers. Popularity is not required for a small package, but these counts provide little external evidence of adoption or community support.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing automated security checks are a modest transparency and maintenance gap.