xervice/yaml-config
It has a usable README, tests, an MIT declaration, and a matching organization-owned repository. The missing security policy and absent security scanning add transparency concerns.
38%
Total Score
50
100
71
50
Health Score Breakdown
The package has made only one release, on July 28, 2018, with no releases in the last 12 months. That long period without updates is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since July 2018.
The repository uses Composer for builds, but no security scanning tool was detected. That is a modest transparency and maintenance concern, not evidence that the package is unsafe.
The repository is not archived, which preserves a path for maintenance, but its last push was still on July 28, 2018 and does not offset the inactivity evidence.
No repository security policy was found. This weakens vulnerability-reporting transparency, although it is secondary to the much stronger abandonment signal.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mike Bertram |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/yaml Version ^4.1.1 | — | — |
xervice/data-provider Version ^1.4.4 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.