zjpay/laravel-cpcn

It has an MIT declaration, useful integration documentation, release notes, no install-time scripts, and only three runtime dependencies. The repository lacks tests, security scanning, and a security policy; pin this version and validate payment flows before production.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is a 154-day-old package with only one release, so there is little evidence of sustained maintenance or release maturity.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Because the package has only one release, this leaves ongoing maintenance unproven and raises abandonment risk.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. For a payment integration, that is a meaningful repository hygiene gap.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities in a package that handles signing and payment messages.

Workflow audit

Both workflows were analyzed with no audit findings or untrusted checkout sinks. However, all three action references are unpinned and one workflow grants top-level write access, creating moderate reproducibility and token-scope concerns.