codehouse/estcard

The README gives basic integration steps, and the dependency surface is small. Included test-key files and the lack of security tooling add operational concern for payment code.

Latest 1.0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The published tree includes testkeys/private.key and testkeys/public.key. Even if these are test credentials, shipping a private key in the artifact is poor release hygiene and warrants caution.

Release history

The package has only two releases, with the latest published in February 2018 and no releases in roughly eight years. That strongly increases abandonment risk, although the package is not marked deprecated.

Repo commit activity

The repository has recorded no commits and no active maintainers in the last three months, consistent with the long gap since its last update. This is a significant maintenance concern for payment integration code.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. That leaves dependency and code-security checks less transparent than they could be.

Security policy

The repository has no security policy, leaving no documented path for reporting vulnerabilities or explaining security expectations. This matters more for code handling payment responses.