mdhesari/finglishtofarsi

The MIT license, README, simple dependency profile, and lack of install-time scripts reduce adoption friction. The small repository and one-person publishing base provide limited evidence that problems or compatibility issues will receive attention.

Latest 0.11

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, with none in the last 12 months; its latest release was about four years ago. This is strong evidence of stalled maintenance for a dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for about four years. This materially increases abandonment risk.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That mismatch raises uncertainty about whether the linked repository actually represents this package.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no community signal to offset the inactive maintenance record.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. The missing scanner is a hygiene gap rather than a standalone severe risk.