medicivn/core
The package includes tests, a changelog, release notes, and a clear MIT declaration. Its single registry maintainer and absent security tooling reduce confidence in ongoing care.
46%
Total Score
33
79
83
Health Score Breakdown
The latest release was in November 2022, and there have been no releases in the last 12 months despite 15 releases overall. This long lapse is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the release gap and indicating no observed ongoing maintenance.
Only one registry account, “Medici Dev,” has publish access. This is a thin publishing base and increases continuity risk, although registry access alone does not establish who actively maintains the code.
There are four open issues, while no issues or pull requests were opened or closed in the last month. This suggests unresolved maintenance demand with no recent response.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Medici Dev |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/http Version ^9.17 | — | — |
illuminate/support Version ^9.17 | — | — |
intervention/image Version ^2.7 | — | — |
illuminate/database Version ^9.17 | — | — |
illuminate/pipeline Version ^9.17 | — | — |
Weekly Downloads
Info
- Last Published
- 3 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.