rogerthomas84/ohdm

Tests, documentation, and licensing are present, with a simple dependency profile. The project shows no commits or releases for about 11 years, and has no security policy, making ongoing support uncertain.

Latest 1.1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only 3 releases, with no release in the last 12 months; its latest release was about 11 years ago. This is strong evidence of abandonment for a library dependency.

Repo commit activity

There were 0 commits and 0 active maintainers during the last 3 months, consistent with the repository having stopped receiving changes about 11 years ago. This materially raises abandonment risk.

Project backing

The package and repository are owned by the same individual account rather than an organization. This is not inherently unhealthy, but it offers no organizational backing to compensate for the inactive project.

Repo popularity

The repository has 0 stars and 0 forks, with 2 watchers. Popularity is only supporting evidence, but these very low adoption indicators provide no meaningful community backstop for an inactive project.

Repo tooling

Composer is used as a build tool, showing basic ecosystem integration, but no security scanning tools are present. The missing scanning is a minor maintenance hygiene gap rather than a standalone severe risk.