haikiri/telebrown

The repository includes tests, matches the package, and has been updated alongside a fast release cadence. The proprietary license has no accompanying license file, and no commits were recorded in the last three months, so long-term maintenance remains uncertain.

Latest 2.12.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

The manifest declares a proprietary license, but no license file was found in either the package or repository. This is a genuine transparency gap for adopters, although it is not evidence of maliciousness.

Project backing

The repository is owned by an individual account rather than an organization, so the single registry maintainer does not benefit from visible organizational backing. This limits demonstrated redundancy but is not severe on its own.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. This conflicts with the rapid registry release cadence and leaves ongoing maintenance capacity uncertain.

Repo popularity

The repository has zero stars and forks and one watcher. Low popularity is only supporting context, but it provides little external evidence of maturity or review.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That is a modest repository hygiene gap rather than evidence that the package is unsafe.