wemersonjanuario/pdf

A README, tests, MIT licensing, and a repository that matches the package make adoption and inspection straightforward. The small community and missing security policy add concern, while the lack of recent work is the main long-term risk.

Latest 1.1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was more than 9 years ago, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a library that may need compatibility updates.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the repository's last push being more than 8 years ago. This materially increases the risk that defects and compatibility issues will remain unresolved.

Repo popularity

The repository has only 5 stars, 1 fork, and 2 watchers. Low adoption is supporting evidence of a small maintenance community, though it is not decisive alone.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning coverage is a modest transparency and maintenance gap for a dependency.

Security policy

The repository has no security policy, so there is no documented path for reporting vulnerabilities or explaining security practices.