michal78/laravel-sms-catcher

Maintainerscaution

Only one registry account has publishing access, which is a modest continuity concern for a user-owned project; the repository evidence shows a second active contributor, partly compensating for that concentration.

Project backingcaution

The registry namespace and repository are owned by the same individual rather than an organization, so continuity depends substantially on that maintainer; recent two-person commit activity provides some compensation.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected; this is a transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for users and maintainers.

Token permissionscaution

Neither workflow declares top-level token permissions. No write permissions were observed, but explicit least-privilege declarations would provide stronger CI security transparency.