The extension is small, clearly packaged, and has a matching source repository. Recent releases and commits show ongoing maintenance, but one contributor carries all recent work and the release workflow has high-confidence injection and pinning weaknesses.
66%
Total Score
63
100
94
83
Only one registry account has publish access. That is a modest publishing concentration for a user-owned project and is reinforced by the repository's single recent contributor.
The source repository is owned by an individual rather than an organization, so the single-maintainer and single-contributor concentration is not compensated by visible organizational backing.
One contributor made all three commits in the last 3 months, giving the project a complete single-person bus factor and increasing continuity risk if that maintainer becomes unavailable.
Composer build tooling is present, but no security-scanning tool was detected. That is a transparency and maintenance gap, though not evidence that the release is unsafe by itself.
The repository has no security policy, leaving no documented path for reporting vulnerabilities in an extension that processes uploaded files and sends email.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^14 | — | — |
felixnagel/pluploadfe Version ^9 || @dev | — | — |
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.