avoo/qcm-core-bundle
The repository has no security policy and almost no community adoption. Its MIT license and lack of install scripts are positives, but they do not offset the maintenance risk.
34%
Total Score
38
100
72
67
Health Score Breakdown
The latest release was published nearly 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment despite four historical releases.
There were no commits or active maintainers in the last 3 months, consistent with the repository's last push being about 9 years ago. This materially raises abandonment risk.
Only one registry account can publish the package. This indicates limited publishing resilience, although registry access alone does not prove who actively maintains the project.
The repository is owned by a user account rather than an organization, so there is no provided evidence of organizational backing to compensate for the thin maintenance base.
There is one open issue and no issue or pull-request activity in the last month. This is limited evidence, but it does not show active community maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jérémy Jégou |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 avoo/qcm-components Version ~1.0 | — | — |
sylius/resource-bundle Version 0.11.*@dev | — | — |
beberlei/doctrineextensions Version *@dev | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 11 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.