xqkeji/composer
There is no published security policy or automated security scanning, leaving project security processes unclear. The package is licensed and documented, with regular releases and recent commits; its maintenance depends on one contributor.
68%
Total Score
67
100
94
75
Health Score Breakdown
The repository owner is an individual account rather than an organization. Combined with one active contributor, this provides no visible organizational redundancy for maintenance.
All 33 commits in the last 3 months came from one contributor, leaving maintenance and continuity dependent on a single person. No organizational backing is shown to compensate for that concentration.
Composer is used as a build tool, but no security scanning tools were detected. For a package distributed as a dependency, that leaves an avoidable security-process gap.
The repository has no security policy. This makes vulnerability reporting and response expectations unclear, though it is a process concern rather than evidence of a malicious package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 xqkeji.cn |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 19 hours ago
- Created
- 3 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.