lnext/auxiliary-solutions
The clear README, MIT licensing, and recent v1.0.6 publication support straightforward adoption. Maintenance depends on one maintainer, with no security policy or scanning and very little community activity.
70%
Total Score
50
100
83
83
Health Score Breakdown
Only one registry maintainer is listed, leaving limited visible publishing capacity and increasing continuity risk if that maintainer becomes inactive.
The package is about 17 months old with four releases and only one release in the last 12 months, indicating a limited release cadence despite the recent v1.0.6 publication.
The repository has zero stars and forks and only one watcher, so there is little observable community adoption or external review to supplement maintainer activity.
Composer is used as the build tool, but no security scanning tools are present, leaving a modest transparency and maintenance-hygiene gap.
The repository has no security policy, so consumers have no documented vulnerability-reporting process; this is a hygiene concern rather than evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Skorilkin Aleksey |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/framework Version ^9|^10|^11|^12|^13 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 year 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.