maxserv/yaml_configuration
It has a clear license, readable documentation, and no install-time scripts. However, maintenance and project security oversight appear to have stopped, making long-term support unlikely.
15%
Total Score
0
64
75
Health Score Breakdown
Packagist marks the entire package as abandoned, with no replacement named. This is a severe adoption warning because the registry no longer presents it as an actively supported dependency.
The package has 17 releases, but the latest was about 8 years ago and there were no releases in the last 12 months. Its early release cadence does not compensate for the prolonged silence.
The repository recorded no commits and no active maintainers in the last 3 months. This strongly indicates that maintenance has stopped, although it does not by itself prove the code is unusable.
Composer is used for the build, which fits the package ecosystem, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.
The repository has no security policy. For a package that imports data and generates configuration, this reduces transparency about how security issues are handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/yaml Version 2.6 - 3.99 | — | — |
typo3/cms-core Version >=6.2.0,<8.8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 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.