nexophp/banner

The organization-owned repository and MIT licensing add useful legitimacy. The tiny README, absent security policy, and lack of security scanning leave little guidance or verification for adopters.

Latest v1.0.1

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a README, but it is only 11 characters and the project has no tests or changelog. Missing tests and changelog are normal packaging practice, while the minimal consumer documentation is a modest transparency gap.

Release history

The package has only two releases, with none in the last 12 months; its latest release was about a year ago. This indicates limited ongoing maintenance, although the release spacing was initially reasonable.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long registry release gap. This is meaningful abandonment risk for a young package.

Repo tooling

Composer is used as a build tool, which is appropriate for the package, but no security-scanning tool is configured. The missing scanning reduces assurance without independently making the release unfit.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a hygiene and transparency weakness, not evidence of unsafe code by itself.