paytm/payment

The MIT license, clear README, and release notes provide useful transparency, while organization ownership and a matching repository support continuity. However, the package has had no releases or commits for about three years, with no tests or security policy, so future compatibility and maintenance are uncertain.

Latest 0.0.3

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, and its latest release was about three years ago. Only three releases exist, which points to inactive maintenance despite the short early release interval.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the package's long release gap and indicating weak current maintenance capacity.

Repo popularity

The repository has zero stars and forks and only four watchers. Popularity is supporting evidence rather than a verdict, but these values provide little evidence of broad community support.

Repo tooling

The repository uses Composer, confirming a defined build tool, but it has no security scanning tools. The missing scanning is a modest transparency and hygiene gap.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a payment integration, even though it does not by itself show an active security problem.