phpnitro/firebase

Usable with caveats: it is a small, clearly packaged, licensed release with recent publishing and an active organization-owned repository. However, the project is only 43 days old, has just two commits in three months from one contributor, and lacks security scanning and a security policy.

Latest v1.2.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is very young at 43 days old, with three releases and a median interval of about 21 days; this shows recent activity but not yet long-term maintenance maturity.

Repo bus factor

One contributor made all two commits in the last three months, creating concentration risk. The organization-owned repository provides some ability to hand maintenance off, so this is a caution rather than a severe risk.

Repo commit activity

Only two commits were recorded in the last three months, with one active maintainer. Recent release activity helps, but the observed development pace is thin.

Repo tooling

Composer is used for builds, but no security scanning tools are configured, leaving a real repository-hygiene gap for a package handling Firebase authentication and cloud calls.

Security policy

No SECURITY.md or equivalent security policy was found, leaving vulnerability-reporting expectations undocumented.