The package has a clear README, tests in the repository, a matching BSD-3-Clause license, and no install-time scripts. Its small ecosystem and absent security scanning add modest concerns, while the unpinned workflow actions weaken build reproducibility.
62%
Total Score
75
100
83
75
The latest registry release was over four years ago, with no releases in the last 12 months; this is meaningful evidence of slowed maintenance despite the package's long history and 12 releases.
There were no commits from any active maintainers in the last three months. The repository's April 2025 push partially offsets this, but current maintenance capacity remains uncertain.
The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little external evidence of adoption.
The repository uses Make and Composer, but no security-scanning tools were detected. Build tooling is a positive, while the missing scanning coverage is a modest transparency gap.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a process gap, not evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
icanboogie/accessor Version ^2.0|^3.0|^4.0 | — | — |
icanboogie/inflector Version ^1.3|^2.0 | — | — |
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.