sumityadav/icici

Documentation and licensing are in place, with a small dependency set and a matching source repository. Treat it as legacy code and verify payment behavior before relying on it in production.

Latest 0.0.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both in October 2015, and none in the last 12 months. That long release gap is a substantial abandonment concern for a payment integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with activity having stopped years ago. This leaves defects and dependency changes unlikely to be addressed.

Maintainers

The registry lists one maintainer, and the project backing identifies an individual-owned repository rather than an organization. A single-person maintenance base increases continuity risk, especially alongside the long inactivity.

Repo popularity

The repository has one star and no forks, indicating very limited adoption. Popularity is supporting evidence only, but it offers little external maintenance or review confidence here.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a payment library, that is a meaningful hygiene gap, though it is secondary to the lack of maintenance activity.