digipeyk/payment-client

Release historydanger

Only two releases were published, both in June 2017, with no release in roughly nine years. This strongly indicates abandonment risk for a dependency.

Repo commit activitydanger

The repository has had zero commits and zero active maintainers in the last three months, consistent with the absence of releases since 2017.

Maintainerscaution

Only one account has registry publish access. That is a thin publishing base and provides little evidence of support continuity for an otherwise inactive package.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, leaving uncertainty that it is the intended source repository.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. This is a modest hygiene gap rather than evidence of unsafe code.