Healthy and suitable to use, with a few security-hygiene caveats. It has frequent releases, active recent development, a clear README and changelog, and a matching source repository; the main gaps are no security policy and undeclared workflow token permissions.
84%
Total Score
70
100
94
80
Only one registry account has publish access, which is a modest publishing continuity risk for a user-owned project. However, repository activity shows a second active contributor, providing some practical compensation.
The package and repository are owned by the same individual user rather than an organization. That limits institutional handoff capacity, but two active contributors and frequent releases provide meaningful compensation.
Two issues were opened in the last month and six remain open, while none were closed during that period. This suggests some unresolved work, but not abandonment given the active commit and release history.
Composer build tooling is present, supporting reproducible project maintenance, but no security scanning tools were detected. This is a security-process gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for a package that handles form protection and server-side endpoints.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4 || ^14.0 | — | — |
typo3/cms-form Version ^13.4 || ^14.0 | — | — |
typo3/cms-fluid Version ^13.4 || ^14.0 | — | — |
altcha-org/altcha Version ^2.0 | — | — |
typo3/cms-backend Version ^13.4 || ^14.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.