anwar/abkash

The MIT declaration, README, and lack of install scripts make the small package easy to inspect and integrate. Its payment-related purpose has no repository security policy, leaving limited support if vulnerabilities emerge.

Latest v1.02

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published on May 8, 2019, about seven years ago, with no releases in the last 12 months. That prolonged release gap is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating a high risk of abandonment.

Project backing

The source repository is owned by an individual account rather than an organization. This is not inherently unhealthy, but it provides less visible backing for a package that has no recent activity.

Repo tooling

Composer is used for the build, but no security scanning tools are present. For a payment-related package, that is a modest transparency and maintenance gap.

Security policy

The repository has no security policy. That leaves users without a documented vulnerability-reporting path, which matters for a package handling payment transactions.