los/lospdf

The package is clearly licensed and includes useful installation documentation. Its small dependency footprint and matching repository improve confidence, while the project remains lightly supported and has no documented security process.

Latest 1.0.1

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in more than 10 years and none in the last 12 months. This is a meaningful freshness concern, despite the six historical releases and relatively regular early cadence.

Repo bus factor

All recent repository commits came from one contributor, so maintenance depends entirely on a single person and could be vulnerable to interruption.

Repo commit activity

The repository recorded one commit in the last three months from one active maintainer. That is some current activity, but it represents only limited maintenance capacity.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance-process gap.

Security policy

The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not by itself evidence that the package is unsafe.