fliglio/web

The package has a clear repository, organization backing, tests, a README, and no install-time scripts. Its lack of security scanning and a security policy leaves maintenance transparency weaker than its packaging quality suggests.

Latest 2.3.3

Packagist

52%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Dependency profile

Six runtime dependencies, including framework and annotation components, create a moderate compatibility surface for a small PHP library. The profile is not unusually large, so this is only a mild concern.

Release history

The package has 20 releases since April 2013, but none in the last 12 months and the latest was published in July 2020—about six years ago. This long release gap is a substantial abandonment concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release inactivity. This lowers confidence that defects or compatibility issues will be addressed promptly.

Repo tooling

The project uses Make and Composer, which supports reproducible development workflows, but no security scanning tools were detected. This is a hygiene weakness rather than evidence of unsafe code.

Security policy

The repository has no published security policy, leaving no documented route for reporting vulnerabilities or explaining supported security handling.