codesren/breezify

The repository has no recent commits or automated security scanning, and registry publishing is handled by one maintainer. A README, matching source repository, MIT declaration, and non-archived repository provide useful transparency but do not offset the lack of demonstrated ongoing maintenance.

Latest 1.0.0

Packagist

45%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published over a year ago, with no releases in the last 12 months. That leaves little evidence of sustained maintenance for a package handling authentication scaffolding.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months. The non-archived status is reassuring, but it does not show that maintenance is continuing.

Maintainers

Only one registry account has publish access. The repository is user-owned rather than organization-backed, so there is no provided evidence of a broader publishing or maintenance base.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a meaningful transparency and maintenance gap for authentication-related software.

Security policy

The repository has no security policy. For a package providing registration, password, email verification, and two-factor authentication scaffolding, this weakens the project's maintenance and disclosure transparency.