zae/strict-transport-security
Clear documentation, tests, MIT licensing, and no install-time scripts reduce adoption friction. The single-maintainer project has no security scanning, so pinning 0.0.3 and checking Laravel compatibility is prudent.
48%
Total Score
33
75
100
Health Score Breakdown
The package has had no release in the last 12 months, and its latest release was in February 2016 after only three total releases. This indicates a long-standing maintenance gap.
The repository recorded zero commits and zero active maintainers in the last three months, providing no evidence of ongoing maintenance.
Only one registry account has publish access. This is a limited publishing base, and the available activity signals do not show compensating current maintenance.
There were no new or closed issues or pull requests in the last month. With no recent commits, this is consistent with an inactive project rather than active stability.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance concern for a dependency with no recent development.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ezra Pool |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/config Version >=1.0 | — | — |
illuminate/support Version >=1.0 | — | — |
symfony/http-kernel Version >=2.0 | — | — |
symfony/http-foundation Version >=2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 11 years 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.