ashita-planning/laravel-error-monitor-xserver

Project backingcaution

The registry namespace and repository owner match, but the owner is a user account rather than an organization. The matching ownership supports authenticity, while it provides limited evidence of maintenance capacity.

Release historycaution

The package is only 43 days old and has two releases, both published within about 6 hours. This is too little history to establish sustained maintenance, although it is not evidence of abandonment by itself.

Repo bus factorcaution

One contributor made 100% of the recent commits, leaving no demonstrated contributor redundancy. The repository is user-owned rather than organization-owned, so there is no provided organizational backing to offset this concentration.

Repo commit activitycaution

Only one commit was recorded in the last three months from one active maintainer. For a package this young that may reflect initial development, but it does not yet demonstrate ongoing maintenance capacity.

Repo toolingcaution

The repository uses Composer and contains testing and analysis configuration, but no security scanning tool was detected. The build setup is present, while security-process transparency is limited.