The package is clearly documented, licensed, narrowly scoped, and backed by an organization, with no runtime dependencies or install scripts. Its long period without releases or repository activity makes future compatibility and maintenance uncertain.
48%
Total Score
75
100
83
88
Only two releases were published, both in May 2015, with no release in roughly 11 years. This is strong evidence of abandonment risk, although the package's narrow scope may reduce its need for frequent changes.
There were zero commits and zero active maintainers in the last three months, consistent with the roughly 11-year release gap and materially increasing abandonment risk.
Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a modest hygiene gap rather than a standalone adoption blocker.
No repository security policy was found. For a small coding-standard package with no runtime dependencies, this is a transparency gap but not a severe dependency risk.
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.