syscover/cms
The README, matching repository, stable versioning, and organization ownership improve transparency. Composer build support is present, but no security scanning or policy leaves maintenance concerns less visible.
38%
Total Score
75
88
75
Health Score Breakdown
The package has only three releases and none in the past 12 months; its latest release was in September 2016, indicating severe staleness despite an earlier regular interval.
The repository recorded no commits and no active maintainers in the past three months, reinforcing the long gap since the latest registry release.
Composer is used as the build tool, showing basic project tooling, but no security scanning tools are configured.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this is a meaningful transparency gap for a CMS package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 SYSCOVER SL |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 syscover/pulsar Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years 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.