mstrychalski/supervisor

The small dependency surface, tests, and clear MIT licensing reduce integration friction. Its last release and repository activity were in July 2018, so maintenance and compatibility risk are substantial.

Latest 1.1.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than eight years: all four releases were published on July 3, 2018. This is strong evidence of abandonment risk, despite the stable version.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the release history and indicating that maintenance capacity is currently absent.

Project backing

The package and repository are owned by the same individual account, so the source linkage is coherent, but there is no organizational backing shown to compensate for the inactive project.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide little evidence of an active user or contributor community.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. This is a modest transparency and maintenance-hygiene gap, not evidence of a defect by itself.