miladimos/conf

The project has a small audience and no recent commit activity, while its last registry release was over four years ago. Clear documentation, tests, a changelog, and a matching source repository provide useful safeguards, but the missing security policy leaves maintenance assurance limited.

Latest v0.5.9

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in over four years, despite eight releases earlier in its history. This is a meaningful abandonment concern for a dependency, even though the repository was pushed more recently.

Repo commit activity

There were no commits and no active maintainers in the last three months. The 2025 repository push is compensating evidence that the project is not clearly abandoned, but current development activity is still absent.

Repo popularity

The repository has five stars and one fork, indicating a small user and contributor base. Popularity is supporting evidence rather than a verdict, but this offers little external maturity evidence.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than a severe dependency risk.

Security policy

The repository has no security policy. For a small package this is not disqualifying, but it reduces transparency about vulnerability reporting and response.