All four workflow actions are unpinned, and the repository has no security policy or scanning tools. The release includes notes and repository tests, but no newer package release or recent commit activity reduces confidence in ongoing maintenance.
57%
Total Score
75
100
88
67
The latest release was published over two years ago, with no releases in the last 12 months. That is a meaningful maintenance concern for a TYPO3 extension, despite five total releases.
There were no commits or active maintainers in the last three months, consistent with the long gap since the last push and increasing abandonment risk.
Composer is used for builds, but no security scanning tools were detected. This is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. That weakens transparency around reporting and handling security issues, though it does not by itself show a defect.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all four action references are unpinned, leaving them exposed to upstream reference changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
in2code/femanager Version ^8.0 || dev-main || dev-develop || dev-eap || dev-eap-v12 | — | — |
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.