sashalenz/binotel-api

Clear documentation, tests in the repository, and regular recent releases support adoption. Recent repository activity has paused, and there is no published security policy or security scanning.

Latest 2.3.1

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. The linked repository is user-owned and active, so this is a limited resilience concern rather than evidence of abandonment.

Project backing

The registry namespace and repository owner match, and the repository is owned by the same individual rather than an organization. This is consistent ownership but provides limited organizational continuity.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months. This weakens evidence of current maintenance, although recent releases and a recent push partly compensate.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a package handling API credentials and webhooks, that is a modest maintenance and transparency gap.

Security policy

The repository has no security policy. This makes vulnerability reporting and response expectations less clear for a package that integrates external API credentials and webhooks.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Oleksandr Petrovskyi

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^10.0\|\|^11.0\|\|^12.0\|\|^13.0	—	—
illuminate/config Version ^10.0\|\|^11.0\|\|^12.0\|\|^13.0	—	—
illuminate/support Version ^10.0\|\|^11.0\|\|^12.0\|\|^13.0	—	—
illuminate/database Version ^10.0\|\|^11.0\|\|^12.0\|\|^13.0	—	—
spatie/laravel-data Version ^4.22	—	—