Clear MIT licensing, a readable package, and repository tests improve transparency. Composer-based builds are straightforward, but missing security documentation and unpinned workflow actions leave modest process risk.
64%
Total Score
67
80
50
The project has released 30 versions over more than six years and published the latest version recently, but only one release appeared in the last 12 months, indicating a slower current cadence.
All 2 recent commits came from one contributor, creating concentrated maintenance risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository recorded only 2 commits in the last 3 months, showing limited recent maintenance activity despite the recent release.
The project uses Composer build tooling, which supports a conventional build process, but no security scanning tools were detected, leaving a modest security-process gap.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4 | — | — |
typo3/cms-backend Version ^13.4 | — | — |
phpoffice/phpspreadsheet Version ^1.30 | — | — |
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.