ttungbmt/filament-ban
The package includes clear licensing, tests in the repository, release notes, and a small dependency set. Its maintenance record is stale, and its automation has avoidable workflow weaknesses. Prefer an actively maintained alternative if this is a core dependency.
43%
Total Score
33
100
88
67
Health Score Breakdown
Only one release exists, published about 4 years and 6 months ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance.
There were zero commits and zero active maintainers in the last 3 months. Combined with the single-release history, this materially raises abandonment risk.
The repository is owned by an individual account rather than an organization. That does not establish poor health, but it provides less visible backing to compensate for the inactive release and commit history.
Six issues and two pull requests remain open, with no new or closed issues or merged pull requests in the last month. This suggests limited recent project response.
The repository has no security policy. For a package that manages user bans and authentication-related behavior, this is a transparency gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Truong Thanh Tung |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 cybercog/laravel-ban Version ^4.7 | — | — |
illuminate/contracts Version ^9.0 | — | — |
spatie/laravel-package-tools Version ^1.9.2 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 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.