mosweed/mosweed_shop_cms
The project has one registry maintainer, no security policy, and no repository security scanning. Its MIT license, matching repository, installation README, and stable release provide useful transparency despite the limited maintenance evidence.
58%
Total Score
50
100
83
75
Health Score Breakdown
Only one registry account has publish access, and project backing identifies a user-owned repository rather than an organization. This leaves limited observable publishing capacity if that maintainer becomes unavailable.
The repository and registry namespace align under the Mosweed user account, and the repository is user-owned. This supports ownership consistency but does not provide organizational maintenance depth.
The package has only two releases, with no releases in the last 12 months; the latest release was about 17 months ago. This points to a materially increased abandonment risk.
There were zero commits and zero active maintainers in the last three months. Combined with the release gap, this is evidence that maintenance has stalled rather than merely being infrequent.
The repository has one star, zero forks, and one watcher. This is weak supporting evidence for maturity, although popularity alone does not determine package health.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mohmad Yazan Sweed |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 livewire/livewire Version ^3.4 | — | — |
illuminate/contracts Version ^8.12|^9.0|^10.0|^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.