booosta/installer

It has a clear license, usable README, and no install-time scripts. A small repository with no security policy and one registry maintainer leaves limited visible oversight.

Latest v4.0.7

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. The repository is user-owned rather than organization-backed, so the narrow publishing base provides limited visible continuity if that maintainer becomes unavailable.

Release history

The package has had no releases in the last 12 months, despite nine releases overall and a latest release about 16 months ago. This indicates stalled maintenance rather than immediate unfitness.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the lack of releases in the last year, this is evidence of currently inactive development.

Repo popularity

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

Repo tooling

The repository uses Composer, which fits the package ecosystem, but it has no reported security-scanning tools. The missing scanning is a modest transparency and maintenance concern.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Peter Buzanits

Direct Dependencies

Dependency	Last Release	Score
booosta/mysqli Version ^4.0	—	—
booosta/adminlte Version ^4.0	—	—
booosta/urlhandler Version ^4.0	—	—
booosta/usersystem Version ^4.0	—	—
booosta/db_privileges Version ^4.0	—	—