Clear documentation, tests, and a license make integration straightforward. The organization-backed project is active, but one contributor and unpinned workflow actions add maintenance and build-reproducibility concerns.
68%
Total Score
83
90
50
The latest registry release was published about five years ago, with no releases in the last 12 months. Recent repository activity partly offsets the stale release cadence, but users may be depending on an aging artifact.
One contributor made all 5 recent commits, creating a concentrated maintenance dependency. Organization backing provides some handoff capacity, but no second recently active contributor is shown.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, both referenced actions are unpinned, which weakens build reproducibility and leaves a modest supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/inflector Version ^1.1|^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.