phpbb/googleanalytics

Clear documentation, release notes, tests, and a recent update make the project straightforward to maintain and integrate. Recent work is concentrated in one contributor, while missing security scanning and unpinned workflow actions add modest operational risk.

Latest 1.2.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 2 recent commits came from one contributor, concentrating current maintenance. The organization-owned repository partly offsets the handoff risk but does not remove it.

Repo commit activity

Only 2 commits were recorded in the last 3 months, so maintenance activity is present but light.

Repo tooling

Composer and Phing provide build tooling, but no security-scanning tools were detected, leaving a modest transparency and maintenance gap.

Security policy

The repository has no security policy, which makes vulnerability-reporting expectations less clear for users and maintainers.

Workflow audit

Both workflows were analyzed with no audit findings or untrusted checkouts, but both action references are unpinned and one workflow grants top-level write permissions. These are workflow hygiene concerns rather than severe risks here because no dangerous trigger or injection sink was found.