The package has had no release or commit activity for over three years, and it remains on 0.1.x. Its tests, README, MIT license, and small dependency footprint are reassuring, but there is no security policy or scanning.
45%
Total Score
75
100
79
83
The latest release was over three years ago, with no releases in the last 12 months and only five releases overall. This materially raises abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the release history showing more than three years without a new release. This is a meaningful maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces assurance, though it is less significant than the prolonged inactivity.
The repository has no security policy. That weakens vulnerability-reporting transparency, especially for a package that affects database query scoping.
Version v0.1.4 is not a stable-major release, so compatibility expectations are lower for consumers. The release is not marked as a prerelease, which partly offsets the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.6 | — | — |
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.