gridguyz/banner

The repository has no security policy or security-scanning tools, and its very small audience provides little evidence of ongoing review. The package is clearly identified, licensed, documented, and not deprecated or archived.

Latest 0.5.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match, so the source appears aligned with the package rather than being a repository mismatch. The owner is an individual account, which provides less organizational continuity than a backed project.

Release history

The latest of six releases was published on April 28, 2014, with no releases in the following 12 years. That long period without a release is strong evidence of abandonment risk.

Repo popularity

The repository has zero stars and forks and one watcher, offering little supporting evidence of community adoption or review. Low popularity alone does not prove the package is unsafe, but it adds to the maintenance concern.

Repo tooling

Composer is used for the build, but no security-scanning tools are present. The missing scanning is a hygiene gap for a package that has been inactive for many years.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, especially when there is no recent maintenance activity to otherwise offset the gap.