Clear documentation, tests, and a declared license make adoption easier. The project lacks security scanning and a security policy, while its single-release history provides little evidence of long-term maintenance.
68%
Total Score
50
100
83
88
The repository is owned by an individual user rather than an organization, and the registry namespace does not add evidence of organizational backing. That leaves the project dependent on a single visible owner, though maintainer activity itself was not collected.
This is the package's first release, published today, with only one release and no established release cadence. That leaves long-term maintenance unproven.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external indication of adoption or review.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a modest transparency and maintenance concern rather than evidence that the package is unsafe.
The repository has no security policy. For a backend extension that handles external URLs and API integrations, this weakens the project's documented process for receiving and handling security reports.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^14.3 | — | — |
symfony/process Version ^7.4 | — | — |
typo3/cms-fluid Version ^14.3 | — | — |
typo3/cms-backend Version ^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.