msp/userlockout
Security documentation and automated scanning are absent, while adoption is minimal. Organization backing and a clear README improve transparency but do not make ongoing support evident.
38%
Total Score
50
100
78
75
Health Score Breakdown
The latest release was published in September 2017, with no releases in the last 12 months and nearly nine years since this version line was updated. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no observed recent maintenance to offset the inactivity.
The repository has 3 stars, 0 forks, and 3 watchers, indicating very limited visible adoption. Popularity is only supporting evidence, but it provides little external confidence here.
Composer build tooling is present, but no security-scanning tool was detected. That weakens evidence of ongoing quality and vulnerability-management practices.
The linked repository has no security policy, leaving no documented path for reporting vulnerabilities in a package that handles login lockout behavior. This is a transparency and maintenance gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Riccardo Tempesta |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 msp/security-suite-common Version >=1.3 | — | — |
magento/magento-composer-installer Version * | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 10 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.