emmanpbarrameda/laravel-scheduled-maintenance

Release historycaution

The package is only 143 days old and all four releases were published within about two hours, so there is little evidence of an established release cadence. Its recent release count is positive but does not offset the very short history.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months. For a package only 143 days old, that leaves a meaningful uncertainty about ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanner is a hygiene gap rather than evidence that the package is unsafe to depend on.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities should be reported. This is a maintenance and disclosure gap, not a severe risk by itself.

Workflow auditcaution

The only workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injections, or audit findings. Both action references are unpinned, which is a supply-chain hygiene weakness but not a severe risk on its own.