pilskalns/f3-wcurl

Clear documentation, tests, licensing, and a matching source repository make adoption easier. The package has a small dependency surface, but its maintenance appears dormant and the repository lacks a security policy or scanning tools.

Latest 1.1

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, providing consistent ownership context but no organizational backing to offset the thin maintenance base.

Release history

The latest release was in October 2018, with no releases in the last 12 months. The package has five releases over its lifetime, so this is a meaningful maintenance concern rather than a brief pause.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates dormant maintenance and raises abandonment risk.

Repo tooling

Composer is used for the build, but no security scanning tools were found. That is a transparency and maintenance gap, though it is not severe enough to make the release unfit by itself.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency for a package that handles external HTTP requests, but it is not evidence of a vulnerability.