Globally configure sanitizing actions for GET/POST parameters.
64%
Total Score
caution
Usable with caveats: maintenance is sparse, with only two releases and no commits in the last three months.
Only one registry maintainer is listed, which limits publishing redundancy for a user-owned project. The repository shows recent release activity, so this is a capacity concern rather than evidence of abandonment.
The package has only two releases across 566 days, with one release in the last 12 months and a median interval of about 439 days. This indicates sparse maintenance, though the latest release is recent enough to avoid an abandonment verdict.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the sparse release history, this lowers confidence in ongoing maintenance.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap, not a standalone reason to reject this small package.
The repository has no security policy. This reduces transparency around vulnerability reporting, although it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-backend Version ~12.4 || ~13.4 || ~14.3 | — | — |
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.