Tests, a changelog, and detailed release notes provide useful project transparency. The prerelease status, sparse release history, and no commits or issue activity in the last three months make ongoing maintenance uncertain.
52%
Total Score
67
81
50
The package is about 2 years and 9 months old with eight releases, but only two releases in the last 12 months and a zero-day median interval suggest a sparse and uneven cadence.
There were zero commits and zero active maintainers during the last three months. Although the recent release shows the project has not vanished, this is a meaningful maintenance warning.
The repository has 10 open issues but no new or closed issues and no merged pull requests in the last three months. That lack of visible issue movement weakens evidence of active maintenance.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and assurance gap, not evidence that the package is unsafe.
The repository has no security policy. For a library that implements PDF parsing and encryption-related functionality, the missing reporting guidance reduces maintenance transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/util Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/exception Version ^3 || dev-FRAMEWORK_6_0 | — | — |
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.