fptron/tron-php

Clear licensing, tests, and a usable README reduce adoption friction. The small dependency surface and matching source repository improve transparency, but the project has not shown recent development activity.

Latest 1.0.5

Packagist

63%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by a user account rather than an organization, so there is no visible organizational backing to offset the small maintainer base.

Release history

All five releases arrived within roughly four days, and no later release is shown despite the package being about nine months old. This brief burst followed by a long release gap lowers confidence in ongoing maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. For a blockchain client library, that is a meaningful sign of stalled maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. This provides no supporting adoption evidence, but popularity is only supporting evidence and does not independently make the package unsafe to depend on.

Repo tooling

Composer build tooling is present, but no security-scanning tools are reported. This is a transparency and hygiene gap rather than evidence that the package is unsafe.