Usable with caveats: this is a mature, stable package with a matching repository, tests, and a clean release artifact, but its last registry release was over five years ago and recent repository activity is absent. Treat it as a maintenance-risk dependency rather than an actively developed one.
62%
Total Score
75
100
89
67
The package has 36 releases since 2012, but none in the last 12 months and the latest release was over five years ago. That long release gap is a meaningful maintenance concern, despite the historically established release cadence.
There were no commits and no active maintainers in the last three months. Combined with no registry releases for over five years, this indicates the package may be largely dormant.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency gap, while the build setup still supports reproducible project maintenance.
No repository security policy was found. This does not make the package unsafe by itself, but it leaves vulnerability-reporting expectations and response procedures unclear.
The repository's workflow does not declare top-level token permissions. No write permissions were observed, but explicitly restricting workflow tokens would provide stronger security hygiene.
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.