aiman/thaana-text-field

It has an MIT declaration, a focused 19-file tree, a useful README, and no install-time scripts. The absence of tests, security scanning, and a security policy limits confidence in future compatibility; pin v1.4.0 if you must use it.

Latest v1.4.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made no release in more than six years, with zero releases in the last 12 months. That is strong evidence of abandonment for a dependency that may need compatibility fixes.

Repo commit activity

There have been no commits and no active maintainers in the last three months, consistent with the release history and reinforcing the risk of abandonment.

Project backing

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the inactive maintenance record.

Repo popularity

The repository has one star and no forks, giving little supporting evidence of broad community adoption or external maintenance.

Repo tooling

Composer is used for builds, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.