Calendarize users can create/edit external calendar imports
62%
Total Score
100
79
50
A post-autoload-dump lifecycle script runs during installation. This adds execution complexity, but the signal alone does not show harmful behavior or make the release unfit.
The package has made no registry release in about 2 years and 10 months, with zero releases in the last 12 months. This is the strongest sign of possible abandonment, although the repository was recently pushed.
The repository uses Composer build tooling, but no security scanning tools are reported. That is a modest transparency and maintenance gap rather than evidence of abandonment.
The repository has no SECURITY.md or other reported security policy. This weakens vulnerability-reporting transparency, though it is not by itself a severe dependency risk.
Version 0.1.2 is not a prerelease, but its 0.x major version indicates the API may still be less mature and more subject to breaking change than a 1.x package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^10.4 || ^11.5 | — | — |
typo3/cms-scheduler Version ^8.7 || ^10.4 || 11.*.*@dev | — | — |
lochmueller/calendarize Version ^12.4 || @dev | — | — |
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.