beatswitch/lock-laravel
The package is MIT-licensed, correctly tied to its source repository, and the repository includes tests and a changelog. Its last release was nearly nine years ago and its repository has had no commits for over eight years, making abandonment a serious concern.
42%
Total Score
50
75
75
Health Score Breakdown
The latest release was in October 2017, with no releases in the last 12 months; the long publication gap materially raises abandonment risk despite a previously regular release cadence.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the last push being over eight years ago and indicating no observed maintenance.
There were no new or closed issues or pull requests in the last month, while three issues remain open; this adds evidence of inactivity but is less severe than the release and commit gaps.
The linked repository has no security policy, which weakens vulnerability-reporting transparency; this is a secondary concern alongside the much stronger maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dries Vints |
| BeatSwitch |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 beatswitch/lock Version ^0.2.0 | — | — |
illuminate/auth Version >=5.3.0 | — | — |
illuminate/support Version >=5.3.0 | — | — |
illuminate/database Version >=5.3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 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.