crcms/repository
The MIT license, readable documentation, tests, and a repository that matches the package support adoption. Its single maintainer and absent security tooling leave less resilience and transparency.
56%
Total Score
25
100
81
75
Health Score Breakdown
The latest release was over six years ago, with no releases in the last 12 months. This is substantial evidence of inactive maintenance despite a history of 25 releases.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and indicating little recent maintenance capacity.
Only one registry account has publish access, limiting publishing redundancy. Because the repository is user-owned rather than organization-backed, this is a real continuity concern.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces automated oversight without making the package unfit by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency and response-readiness gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 crcms/event Version ~1.0.0 | — | — |
illuminate/cache Version ^5.5|^6.0 | — | — |
illuminate/console Version ^5.5|^6.0 | — | — |
illuminate/support Version ^5.5|^6.0 | — | — |
illuminate/database Version ^5.5|^6.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 9 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.