skeeks/cms-seo
Clear licensing, documentation, tests, and a clean package layout support adoption. The project has one active contributor and no security policy, so maintenance continuity depends heavily on the organization.
82%
Total Score
67
100
94
88
Health Score Breakdown
One contributor made 100% of the recent commits. Organization backing provides some handoff capacity, but no second active contributor is shown, leaving a meaningful continuity risk.
There were 3 commits in the last 3 months, showing current activity, but all came from one maintainer. The activity is positive while the concentration limits continuity.
Composer is used as the build tool, but no security scanning tools were detected. This is a modest supply-chain hygiene gap rather than evidence of abandonment.
The repository has no published security policy. This is a transparency gap for reporting and handling vulnerabilities, although it does not by itself indicate unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Semenov Alexander |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 skeeks/cms-job Version ^1.0 || dev-master | — | — |
skeeks/cms-agent Version ^3.2 || dev-master | — | — |
Weekly Downloads
Info
- Last Published
- 1 hour ago
- Created
- 10 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.