Laravel middleware for forcing https connection
55%
Total Score
50
88
75
One registry maintainer is responsible for publishing the package. That is plausible for a small personal project but provides limited maintenance redundancy.
The latest release was published about 8 years ago, with no releases in the last 12 months. This is the strongest evidence of stale maintenance, although the package may be functionally stable.
There were no commits and no active maintainers in the last 3 months. Combined with the old release history, this supports a meaningful abandonment concern.
Composer is used for the build, but no security scanning tools were detected. This is a maintenance and transparency gap, though it is less significant for this very small middleware package.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.