rogerthomas84/daemoniser

The README is present, the package maps cleanly to its repository, and installation has no lifecycle scripts. The single maintainer, absent tests and security policy, and minimal project activity leave little ongoing assurance.

Latest 1.1.5

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in December 2019, with no releases in the last 12 months; this indicates nearly seven years without demonstrated maintenance.

Maintainers

Only one registry maintainer is listed. That is consistent with this user-owned project, but it leaves little visible publishing redundancy if the maintainer becomes unavailable.

Project backing

The repository is owned by the same individual namespace as the package, with no organization backing indicated. This is coherent ownership but offers limited institutional continuity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide no supporting evidence of broad review or community resilience.

Repo tooling

Composer is used as the build tool, but no security-scanning tooling is present; this is a modest transparency and maintenance gap for a dependency project.