Keep track of developer logs. Provides automatic email notification about important errors.
62%
Total Score
caution
Usable with caveats: maintenance is concentrated in one contributor and workflow hygiene is weak.
One contributor made all 3 commits in the last 3 months, creating a concentrated maintenance path. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Only 3 commits were made in the last 3 months, indicating limited recent activity. The active release history partly compensates, but the repository signal remains a mild maintenance concern.
The project uses Composer, but no security scanning tool was detected. For a package with release workflows, that is a modest transparency and maintenance gap.
The repository has no security policy. This makes vulnerability reporting and response expectations less clear for downstream users.
Both workflows were analyzed, but all 11 action references are unpinned, and a high-confidence template-injection finding appears in the release workflow. No untrusted checkout or dangerous trigger was reported, so this is workflow hygiene risk rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ~2.13.1 || ^3.6 || ^4.0 | — | — |
typo3/cms-core Version ^v12.4.2 || ^13.4 | — | — |
graylog2/gelf-php Version ~1 || ^2.0 | — | — |
typo3/cms-scheduler Version ^v12.4 || ^13.4 | — | — |
symfony/rate-limiter Version ^6.4 || ^7.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.