dosarkz/epay-kazcom

Release historydanger

The latest registry release was over 8 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having six historical releases.

Licensecaution

No declared license, license file, or repository license file was detected. This creates a real legal and adoption concern for a dependency.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months. The repository is not archived, but current development activity is absent.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This limits evidence that dependency or code vulnerabilities are routinely checked.

Security policycaution

The repository has no security policy, leaving vulnerability reporting expectations unclear. This is a transparency gap, though it is less severe than the maintenance concerns.