hamoda-dev/configure

The release is licensed, documented, and has no install-time scripts, which reduces adoption friction. Its user-owned project has no security scanning and limited contributor capacity, making future fixes less dependable.

Latest 1.0

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published over six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and weakening confidence in ongoing maintenance.

Maintainers

Only one registry account can publish the package. Because the project is backed by a user-owned repository rather than an organization, this indicates limited publishing capacity, though it does not by itself prove abandonment.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a maintenance and transparency gap, though it is secondary to the inactivity evidence.