Common deployer configuration for TYPO3 projects
68%
Total Score
67
100
94
75
The repository recorded zero commits and zero active maintainers in the last 3 months, which raises a maintenance and abandonment concern; the recent push and release history partly offset it.
There is one open issue and one open pull request, but no issues or pull requests were opened or closed in the last month, providing little evidence of active community handling.
Composer is used for builds, but no security scanning tool is configured, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users lack documented guidance for reporting vulnerabilities or understanding the project's security process.
The only workflow is fully analyzed and has no detected findings; its pull_request_target trigger is harmless here because there are no untrusted checkouts or script injections. However, its one action use is unpinned, weakening supply-chain reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
helhum/typo3-console Version ^8.2.3 | — | — |
helhum/dotenv-connector Version ^3.2.0 | — | — |
sourcebroker/deployer-extended Version ^24.0.0 | — | — |
sourcebroker/deployer-typo3-media Version ^1.0.0 | — | — |
sourcebroker/deployer-typo3-database Version ^1.0.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.