ipfy/homoglyph

This is a well-scaffolded, clearly licensed v1.0.0 package with tests, documentation, a matching organization-owned repository, no deprecation, no install-time lifecycle scripts, and a modest runtime dependency profile. However, it was released today with only one release, the repository has no observed commits or active maintainers in the last 3 months, has no security policy or security-scanning tooling, and has no popularity or issue-activity history. These weaknesses may primarily reflect the package’s immediate age rather than abandonment, but there is not yet enough release or maintenance history to treat it as a mature dependency.

Latest v1.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release and is 0 days old, so there is no release cadence or historical evidence of sustained maintenance yet. This is a meaningful maturity concern, though the package’s newness prevents it from independently proving abandonment.

Repo commit activity

The repository records zero commits and zero active maintainers in the last 3 months. Because the release is 0 days old, this likely reflects limited observation history rather than demonstrated abandonment, but it leaves maintenance capacity unverified.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. This is ambiguous for a repository released today, but it provides no evidence of an established feedback or maintenance process.

Repo popularity

The repository has zero stars, forks, and watchers. Given that the package is newly released, this is weak supporting evidence rather than a severe concern, but there is no external adoption signal yet.

Repo tooling

Composer build tooling is present, but no security-scanning tools are detected. This is a repository hygiene gap, not evidence that the package is unsafe or unmaintained.