woldy/cms
It includes tests, a README, an MIT license, and no install-time scripts. The single maintainer, absent security policy and scanning, and repository name mismatch add adoption risk.
38%
Total Score
25
100
69
75
Health Score Breakdown
The package was first released about 8 years ago but has had no releases in the last 12 months, and its latest release was in January 2018. This strongly indicates abandonment risk.
There were no commits and no active maintainers in the last 3 months, consistent with maintenance having stopped for about 8 years.
Only one registry account has publish access. For this user-owned project that is a thin publishing base and increases continuity risk, especially alongside the lack of recent activity.
The repository name does not match the package name, and the README was not confirmed to mention the package. That creates uncertainty about whether the linked repository is the package's intended source.
Composer build tooling is present, but no security-scanning tools were detected. That leaves a transparency and maintenance-hygiene gap for a package with no recent activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 woldy |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 mews/captcha Version ^2.1 | — | — |
laravel/framework Version >=5.3.1 | — | — |
barryvdh/laravel-debugbar Version ^2.3 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.