An organization-backed repository remains unarchived, has tests, and received a commit within the last three months. The package is licensed and documented, but its single recent contributor and absent security policy leave limited evidence for broader maintenance.
67%
Total Score
83
100
88
67
The package has had no registry release in more than three years, despite seven releases overall. Recent repository activity partly offsets the stale release cadence but does not remove the maintenance concern.
Only one commit was recorded in the last three months, by one active maintainer. This shows some current activity but a limited recent maintenance pace.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence of unsafe behavior.
The repository has no security policy. For a TYPO3 extension this reduces the clarity of vulnerability reporting and maintenance expectations, though it does not indicate abandonment by itself.
The single workflow was fully analyzed with no untrusted checkout or script-injection findings, but both referenced actions are unpinned. The missing top-level permissions block is ordinary; unpinned actions remain a supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^9.5.29 || ^10.4.35 | — | — |
jweiland/service-bw2 Version ^4.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.