async-aws/scheduler

The repository has had no commits or active maintainers in the last three months, despite two releases in the last year. All four workflow actions are unpinned and the project has no security scanning, while organization backing, licensing, tests, and release documentation support continued use.

Latest 1.6.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, a meaningful sign of slowed maintenance. The recent release history partly offsets this, but does not remove the abandonment concern.

Repo tooling

The repository uses Composer and Make, but no security scanning tools were detected, leaving a maintenance and security-hygiene gap.

Security policy

No security policy was found in the repository, which reduces transparency for reporting and handling vulnerabilities.

Workflow audit

Both workflows were analyzed completely with no dangerous triggers, untrusted checkouts, or audit findings. However, all 4 action references are unpinned, weakening build reproducibility and supply-chain hygiene; the absence of top-level permissions is acceptable on its own.