digitalclaim/azure-scheduler-laravel

Release historydanger

Only one release exists, from over two years ago, with no releases in the last 12 months. This is strong evidence of limited maintenance for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the single old release, this indicates currently inactive maintenance.

Workflow auditdanger

All five workflows were analyzed, but all 12 action references are unpinned, three workflows grant top-level write access, and a high-confidence bot-conditions finding affects Dependabot auto-merge. The pull_request_target trigger has no untrusted checkout or script-injection sink, so it is not dangerous on its own.

Repository archivedcaution

The repository is not archived, although its last push was in July 2024; the active repository status partly offsets abandonment concerns but does not overcome the stale release record.

Security policycaution

The repository has no security policy. This is a transparency gap, though it is less serious than the package's inactive release and commit history.