mteu/typo3-monitoring
Clear documentation, a license, and release notes support adoption. The install-time script and absent repository security scanning warrant extra operational review.
70%
Total Score
75
94
67
Health Score Breakdown
A post-install command runs during installation, adding execution-time supply-chain and deployment complexity compared with a package without lifecycle scripts.
All 52 recent commits came from one contributor, so maintenance depends heavily on a single person despite the strong recent activity.
Composer is used for builds, but no security scanning tools were detected. This is a transparency and defense-in-depth gap, not evidence that the release is unsafe.
All four workflows use read-only permissions and all 25 analyzed action references are pinned, but the release workflow has four high-confidence template-injection findings. With no untrusted checkout or script-injection trigger reported, this remains a workflow hygiene concern rather than a severe standalone risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Martin Adler |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^3.0 | — | — |
psr/clock Version ^1.0 | — | — |
symfony/mime Version ^7.4 | — | — |
doctrine/dbal Version ^4.4 | — | — |
symfony/mailer Version ^7.4 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 1 year ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.