goodway/laravel-nats

Project backingcaution

The registry namespace and repository are owned by the same individual account, which supports package-to-repository alignment but provides no organizational maintenance redundancy.

Repo bus factorcaution

One contributor made all commits during the last 3 months, leaving maintenance dependent on a single active person. The linked repository is user-owned rather than organization-owned, so there is no shown backing to offset that concentration.

Repo commit activitycaution

Only one commit was recorded in the last 3 months, so recent maintenance activity is present but thin. This lowers confidence in sustained support.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, although it does not by itself indicate that the package is unsafe.