professionalweb/payment-laravel-cnp

Release historydanger

The latest release was in November 2018, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a payment integration.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push, this indicates that maintenance capacity has effectively disappeared.

Package scaffoldingcaution

The artifact has no README, tests, or changelog, though a GitHub release for this exact version provides release notes. The missing README and tests reduce consumer guidance and confidence in a payment package.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of community support for a payment package.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tool is configured. The missing scanner is a hygiene gap rather than proof of unsafe code.