The package has useful documentation, tests, a changelog, and a clear MIT license. Recent registry releases contrast with no repository commits in the last three months, while security scanning is absent and the single-publisher setup limits resilience.
65%
Total Score
50
93
50
One registry account can publish the package. The repository is user-owned rather than organization-backed, so the narrow publisher base gives less operational resilience.
There were zero commits and zero active maintainers in the last three months. That is a meaningful maintenance concern, especially alongside eight open pull requests.
No issues or pull requests were opened or closed in the last month, although eight pull requests remain open. This suggests limited recent review or integration activity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces automated supply-chain hygiene, though it is not by itself evidence of unsafe code.
The repository has no security policy, leaving no documented route for reporting or handling vulnerabilities. This is a transparency gap for a library that processes documents.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
setasign/fpdi Version ^2.6 | — | — |
symfony/process Version ^6.4 || ^7.0 | — | — |
tecnickcom/tcpdf Version ^6.10 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.