imedge/simple-daemon

The project has no recent development activity and only two releases, both published about two years ago. Its MIT license, tests, and organization-owned repository provide useful baseline transparency, but the tiny README and unpinned workflow actions add maintenance and build-reproducibility concerns.

Latest v0.2.0

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, with none in the last 12 months, and its latest release was about two years ago. This is strong evidence of low maintenance activity for a dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the stale release history and increasing abandonment risk.

Package scaffolding

The package includes tests and a README, but the README is only 14 characters and there is no changelog. Tests are a positive, while the very limited consumer documentation is a real transparency gap for a library.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a modest transparency gap, especially for a package intended to run daemon processes.

Workflow audit

All six analyzed action references are unpinned, which weakens build reproducibility. The audit found no dangerous triggers, sinks, or other findings, and missing top-level permissions blocks are acceptable here, so this is a hygiene caution rather than a severe workflow risk.