crudadmin/payments

Its dependency set is modest and install scripts are absent. The lack of tests, a README, security policy, and security scanning leaves less evidence for safe maintenance, while the organization-backed source remains active.

Latest 1.2.5

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package contains neither a README nor tests, but missing tests and changelog files are normal for published artifacts. The absent README is a minor consumer-documentation gap for a Laravel integration library.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This gives little evidence of community engagement, but it is not by itself evidence of abandonment.

Repo popularity

The repository has zero stars and forks and one watcher. Low popularity limits community validation, but popularity is supporting evidence and does not outweigh the active release history.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem. No security scanning tools are configured, leaving a modest security-process gap.

Security policy

The repository has no security policy. For a package handling payment integrations, this reduces transparency around vulnerability reporting and response.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Marek Gogoľ

Direct Dependencies

Dependency	Last Release	Score
crudadmin/crudadmin Version ^4.0\|^5.0\|dev-master\|dev-5.0-dev	—	—
marekgogol/invoices Version ^4.0\|dev-master	—	—
gopay/payments-sdk-php Version ^1.4	—	—