Middleware for forcing HTTPS
61%
Total Score
caution
Usable with caveats: release and commit activity have been quiet for nearly two years.
Only one account has registry publish access, leaving little visible publishing redundancy. Because the project is user-owned, this is a real but moderate continuity concern rather than evidence of a missing organization.
The registry namespace and repository are both owned by the same individual, providing consistent ownership context. It does not provide the redundancy of organization backing.
The package has six releases since September 2022, but no releases in the last 12 months; the latest release was nearly two years ago. Its earlier roughly three-day median interval shows it was previously active, which softens but does not remove the maintenance concern.
There were no commits and no active maintainers in the last three months. Combined with the old last push, this indicates a quiet project rather than current active maintenance.
Composer is used as the build tool, which fits the package, but no security scanning tool is configured. That leaves a modest transparency and maintenance-hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^11.5 || ^12.4 | ^13.4 | — | — |
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.