Usable with caveats: the package is licensed, documented, tested, and backed by a matching repository, but it has had no release or commit activity for about 4 years and 6 months. Its 0.x version and limited repository security controls add maintenance risk.
57%
Total Score
50
100
83
80
The repository had zero commits and zero active maintainers in the last 3 months; together with the 2022 latest release, this indicates maintenance has effectively stopped for about 4 years and 6 months.
Only three releases have been published since March 2016, with no releases in the last 12 months and a median interval of about 3 years. This is a meaningful sign of slow maintenance for a dependency.
There were no new or closed issues or pull requests in the last month, with one issue currently open. This is consistent with a quiet project and provides little evidence of active maintenance.
Composer build tooling is present, but no security scanning tools were detected. That limits automated security and maintenance visibility, although it is not by itself evidence of an unsafe package.
The repository has no security policy, leaving no documented process for reporting and handling vulnerabilities. This is a transparency gap for a package used in application configuration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hassankhan/config Version ^0.10.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.