Usable with caveats: the package is licensed, small, focused, and backed by an organization with a recent release. Its three-release history and zero commits or active maintainers in the last three months indicate limited maintenance capacity, and the repository has no security policy or scanning.
65%
Total Score
67
100
83
88
The package is about 5 years and 5 months old but has only three releases, with a median interval of about 2 years and 8 months. One release in the last 12 months shows some recent activity, but the overall cadence is sparse.
The repository recorded zero commits and zero active maintainers in the last three months. Although the recent push and release are compensating evidence, the current maintenance capacity still appears thin.
There are no open issues or pull requests and no activity in the last month. This avoids an unresolved backlog, but it also provides little evidence of an active user or maintainer community.
The repository has zero stars and forks and only four watchers, indicating little external adoption or review. Popularity is supporting evidence rather than a decisive health measure, so this is a modest concern.
Composer build tooling is present, but no security scanning tools were detected. For a library handling configuration access, the missing automated security checks reduce transparency.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.