bobbydum/number-to-words

Tests, clear licensing, and a small dependency surface support dependable use. The lack of a security policy and scanning leaves fewer safeguards if maintenance resumes slowly.

Latest 2.2.6

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, giving clear ownership but no organizational backing to compensate for the inactive history.

Release history

The package is mature at 1,682 days old with 56 releases, but it has had no releases in the last 12 months and its latest release was in February 2022, indicating prolonged inactivity.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and raising maintenance risk.

Repo issue activity

There was no issue or pull request activity in the last month and no pull requests were merged, providing no recent evidence of ongoing maintenance.

Repo tooling

Composer and Make are used for project tooling, but no security scanning tools are configured, leaving a modest repository hygiene gap.