3neti/emi-core
Usable with caveats: it is actively maintained, tested, and clearly tied to its source repository, but it is a young project controlled by one contributor and uses a proprietary license. Confirm the licensing terms and have a plan for maintenance continuity before adopting it broadly.
72%
Total Score
63
100
88
90
Health Score Breakdown
The package declares a proprietary license and has no license file in the artifact or repository, which can restrict reuse and leaves licensing terms less transparent than a standard open-source license.
Only one registry account has publish access. This is a continuity concern, although registry access alone does not establish who actively maintains the project.
The registry namespace and repository owner match, but the owner is a user rather than an organization, so there is no organizational backing to offset the concentrated maintainer base.
One contributor made all 21 commits in the last three months, creating a genuine single-person continuity risk with no second active contributor shown.
No security policy is present. This is a transparency gap for a package handling settlement, funding evidence, and webhook-related functionality, and no provided signal compensates for it.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Lester Hurtado |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version ^12.0 || ^13.0 | — | — |
spatie/laravel-data Version ^4.0 | — | — |
lorisleiva/laravel-actions Version ^2.9 | — | — |
Weekly Downloads
Info
- Last Published
- 24 days ago
- Created
- 5 months 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.