nmcquay/pagerduty

The README, tests, MIT declaration, and small dependency set provide a clear, lightweight package baseline. Its repository has no recent commit or issue activity, and there is no security policy, leaving maintenance and security response uncertain.

Latest 0.1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the repository remaining available.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months, consistent with a project that is no longer actively maintained. The 2018 last-push date reinforces the abandonment concern.

Project backing

The package and repository are owned by the same individual account, and the repository is not organization-backed. That is consistent ownership, but it provides a thinner maintenance capacity than demonstrated organizational backing.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with one issue still open. This indicates little current project attention and provides no evidence of an active maintenance process.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. This is a maintenance and assurance gap, though it is less significant than the long-standing inactivity.