The artifact declares MIT but its license file is GPL-3.0, creating a real compatibility question. Tests, documentation, a stable release, and no install scripts provide useful safeguards despite the inactive project.
55%
Total Score
50
81
83
The manifest declares MIT, but the detected LICENSE file is GPL-3.0. Because a license is present this is not an absence of licensing, but the mismatch requires compatibility review.
The package has made no releases in the last 12 months, and its latest release was about 4 years ago; its earlier six-release history shows initial activity but not ongoing maintenance.
The repository recorded zero commits and zero active maintainers over the last 3 months, consistent with the roughly 4-year gap since the last push and release.
Composer build tooling is present, but no security scanning tools were detected, reducing automated coverage for a package that has otherwise remained inactive.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a modest transparency gap for a maintained dependency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
setasign/tfpdf Version ^1.32 | — | — |
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.