ianliao/linebot

The MIT license, README, release notes, and small dependency set make inspection straightforward. A single maintainer and absent security tooling leave limited ongoing project support.

Latest v1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both in August 2023, and none in more than three years. This is strong evidence of abandonment risk, despite the repository not being archived.

Maintainers

Only one registry account has publish access. That is a limited publishing base for a user-owned project and increases continuity risk when combined with the lack of recent activity.

Project backing

The package namespace and repository are owned by individual accounts rather than an organization. That is not inherently unhealthy, but it offers less visible institutional backing for a project already lacking recent activity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of a broad support community.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. This is a hygiene gap that matters more for long-term maintenance than for basic package structure.