paysera/lib-api-bundle

The package is clearly documented, tested, licensed, and backed by an organization. Its long pause in releases and commits makes ongoing fixes uncertain, while unpinned workflow actions and no security scanning add hygiene concerns.

Latest 1.8.1

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 15 releases since December 2019, but none in the last 12 months and its latest release was about 18 months ago. That weakens confidence in ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the roughly 18-month release pause. This creates a real risk that compatibility and security fixes may not arrive promptly.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with one issue still open. This is a mild maintenance warning, but the low issue volume is not severe by itself.

Repo tooling

Composer is used for the build, but no security-scanning tool was detected. That is a repository hygiene gap, especially for a framework integration with multiple runtime dependencies.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, but not evidence that the package is unsafe.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
psr/log Version ^1.0\|^2.0	—	—
symfony/validator Version ^3.4.34\|^4.3\|^5.4\|^6.0	—	—
doctrine/annotations Version ^1.14 \|\| ^2.0	—	—
doctrine/persistence Version ^1.3.8 \|\| ^2.0.1 \|\| ^3.0	—	—
paysera/lib-pagination Version ^1.0	—	—