kjos/kjos-laravel-parameter-mapper

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base for a user-owned project and increases continuity risk, though registry access alone does not measure actual contribution activity.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no observed organizational backing to offset the thin maintainer base.

Release historycaution

All 25 releases occurred within one day, and the latest release was about 10 months ago. This looks like an initial burst followed by limited visible maintenance, although the package is still relatively young.

Repo issue activitycaution

There are no open issues or pull requests, and no issue or pull-request activity in the last month. This provides no evidence of active maintenance, but it also shows no unresolved backlog.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than a standalone severe risk.