The MIT declaration, tests, and release notes improve transparency. Install-time scripts and no security policy add operational uncertainty; the young project has little track record.
58%
Total Score
0
86
50
The repository recorded zero commits and zero active maintainers over the last three months. For a package released only a few months ago, that is a meaningful maintenance and abandonment concern.
The package runs post-install and post-update commands, increasing installation complexity and the amount of code executed during dependency changes. No provided signal shows those scripts are safely constrained.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no outside adoption signal to compensate for the thin maintenance history.
Composer build tooling is present, but no security scanning tools were detected. That is a process gap for a package handling financial functionality, though it is not evidence of unsafe code by itself.
The repository has no security policy. This weakens transparency about vulnerability reporting and response expectations for a package used in financial applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nnjeim/world Version ^1.1 | — | — |
dompdf/dompdf Version ^3.1 | — | — |
mitoteam/jpgraph Version ^10.5 | — | — |
smalot/pdfparser Version ^2.12 | — | — |
maatwebsite/excel Version ^3.1 | — | — |
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.