madkom/gitlab-ci-private-runner
The package includes a useful README, tests, and a modest runtime dependency set. It lacks a security policy and automated security scanning, so ongoing maintenance and release confidence are limited.
38%
Total Score
100
64
50
Health Score Breakdown
The latest release was published in May 2016, about 10 years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment despite seven total releases.
The repository has 4 stars and 1 fork, providing little community evidence to compensate for the long period without releases or updates.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a maintenance and assurance gap, though it is not evidence of malicious behavior.
The repository is not archived, which preserves a path for future maintenance, but its last push was in May 2016 and does not offset the very old release history.
The repository has no security policy. For a tool that runs CI jobs in Docker, this reduces transparency around reporting and handling security issues.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dariusz Gafka |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/yaml Version ^3.0.5 | — | — |
symfony/console Version ^3.0.5 | — | — |
symfony/process Version ^3.0.5 | — | — |
symfony/dependency-injection Version ^3.0.5 | — | — |
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.