Healthy and suitable to use, with a clear license, active organizational backing, recent repository work, tests, and a documented 4.0.0 release. The main concerns are no registry release in over a year and all recent commits coming from one contributor, plus incomplete workflow permission declarations.
78%
Total Score
88
100
88
88
The package has existed since 2013 with 27 releases, but it had no registry release in the last 12 months and its latest release was over a year ago. Recent repository activity partly compensates for the slower registry cadence.
All three recent commits came from one contributor, creating a meaningful continuity risk. Organizational backing reduces the risk somewhat because maintenance can potentially be handed off, but no second active contributor is shown.
Composer build tooling is present, supporting a reproducible project structure, but no security scanning tools were detected; the security gap is limited because other repository security controls are present.
The CI workflow lacks top-level token permissions, so its default permissions are not explicitly constrained. No write permissions were observed, but explicit least-privilege configuration would improve transparency.
| Title | Versions | Severity |
|---|---|---|
CVE-2022-23799 joomla/input is vulnerable to Security Vulnerability in versions 2.0.0 - 2.0.2. | 2.0.0 - 2.0.2 | Critical |
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
joomla/filter Version ^4.0 | — | — |
symfony/deprecation-contracts Version ^2|^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.