sebastienheyd/active

The package is small and clearly documented, with tests and a source repository that matches the package. Its slow release cadence, no recent commit activity, and missing security policy leave maintenance and response capacity uncertain.

Latest 1.3.1

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by the same individual as the registry namespace, so ownership is consistent and does not suggest an unrelated publishing account. Individual ownership also means the visible maintainer base is relatively narrow.

Release history

The package has five releases over about three and a half years, with two releases in the last 12 months, but the median interval is about 11 months. That is a slow maintenance cadence for a dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Although the recent release shows the project can still publish, current development activity is limited.

Repo tooling

The repository uses Composer and Make, but no security-scanning tooling was detected. For a small package this is a hygiene gap rather than a severe dependency risk.

Security policy

The repository has no security policy. That makes reporting and handling future vulnerabilities less transparent, though it does not by itself show that the package is unsafe.