Its MIT licensing and complete five-file artifact make inspection straightforward. There is no security policy or automated security scanning, so maintenance depends on one publisher.
38%
Total Score
0
71
83
The package has only two releases, with the latest published in March 2017 and none in the past 12 months. This long period without releases is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the release history showing no activity since 2017. The repository is not archived, but there is no observed maintenance to offset the gap.
Composer build tooling is present, but no security scanning tools are configured. The build setup is a small positive, while the missing security automation leaves a maintenance and assurance gap.
The repository has no security policy. For a small package this is a transparency gap, and no provided signal shows a documented process for handling vulnerabilities.
Version v0.1.1 is not a stable major release, which limits maturity evidence, although it is not marked as a prerelease. Combined with the very limited release history, this adds a modest maturity concern.
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.