blesta/realtime_register

This release appears usable and reasonably supported by an organization-owned repository, a non-deprecated stable version, recent release activity, and a small dependency surface. However, maintenance evidence is mixed: the repository had no commits or active maintainers in the last 3 months, while the package provides no tests or changelog and has no security policy or security-scanning tooling. The package is not an obvious abandonment risk because it was released recently and has recent pull-request merges, but these transparency and maintenance gaps warrant caution before adopting it as a critical dependency.

Latest 2.0.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present, but the artifact and repository have no tests or changelog. For a module with integration-facing behavior, the lack of visible verification and change documentation lowers transparency.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers during the last 3 months. This is a meaningful maintenance concern, although it is partly offset by the recent release and recent merged pull requests.

Repo popularity

The repository has 0 stars, 1 fork, and 3 watchers, showing limited external adoption or review. Popularity is supporting evidence rather than decisive, but this provides little independent validation.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured. The build setup is appropriate for the package ecosystem, while the missing security automation is a transparency and assurance gap.

Security policy

The repository has no security policy. For a package that integrates with registrar APIs and manages domain-related operations, the missing vulnerability-reporting guidance is a genuine security transparency gap.