bseries/cms_team
The license, matching source tree, and organization ownership provide useful transparency. Its small, stable scope helps, but future compatibility support is uncertain for a modern project.
38%
Total Score
50
100
75
75
Health Score Breakdown
The latest release was on July 10, 2018, and there were no releases in the last 12 months. This long release silence is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months, consistent with a repository whose last push was in August 2019. This materially increases abandonment risk.
The repository has zero stars and forks and one watcher. Low visibility is supporting caution, though popularity alone is not decisive for a small module.
Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unfit by itself.
The repository has no security policy. For a small, inactive package this weakens vulnerability-reporting transparency, though it is less severe than the maintenance gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 bseries/cms_core Version ^1.5 | — | — |
bseries/base_core Version ^1.5 | — | — |
bseries/base_media Version ^1.5 | — | — |
unionofrad/lithium Version ^1.2 | — | — |
composer/installers Version 1.*@stable | — | — |
Weekly Downloads
Info
- Last Published
- 8 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.