kentjerone/laravel-chain-rule

Maintainerscaution

Only one registry account has publish access. The repository is user-owned rather than organization-backed, so there is limited observable publishing redundancy.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. This is a meaningful maintenance concern, especially for a single-owner project, although the recent release history provides some compensating evidence.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, but it does not by itself make the release unfit to use.

Workflow auditcaution

Both workflows were analyzed without audit findings or untrusted-code sinks, but all 7 action references are unpinned and one workflow grants top-level write permissions. These are workflow hygiene concerns, not severe risks on their own.