jord-jd/laravel-malware-validation-rule

Maintainerscaution

Only one registry account has publish access, which creates publishing continuity risk; the matching repository and recent activity provide some evidence of active ownership but do not remove the single-publisher concentration.

Project backingcaution

The package and repository are owned by the same individual user account, establishing direct ownership but not the redundancy or handoff capacity of organization backing.

Release historycaution

The package is mature and has two releases in the last 12 months, including a recent release, but its three-release history and roughly three-year median interval show an uneven cadence.

Repo bus factorcaution

All recent commits came from one contributor, so maintenance depends entirely on that person; the repository is user-owned rather than organization-owned, so there is no provided organizational backing to offset the concentration.

Repo commit activitycaution

There was one commit in the last three months from one active maintainer, showing recent maintenance but a very limited recent activity level.