The repository is quiet, with no commits in the past three months and no releases in the past year. Its clear licensing, minimal dependency surface, and organization backing reduce adoption concerns, but the lack of security policy leaves a notable transparency gap.
58%
Total Score
75
100
81
75
The package has four releases across about 7 years, with no release in the past 12 months and a median interval of about 28 months. This suggests slow maintenance, though the latest release is recent enough to avoid an abandonment verdict.
There were no commits and no active maintainers in the past three months. That is a meaningful maintenance concern, although the repository is not archived and has a recent release.
The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but this offers little external validation.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. For a package used in applications, this leaves vulnerability-reporting expectations unclear.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.