Its dependency surface is small, and the package is not deprecated or archived. However, it has had no release or commit activity since August 2017, and the linked repository neither matches the package name nor mentions it, making current maintenance and package ownership unclear.
35%
Total Score
38
100
44
75
The package has only three releases, all clustered in August 2017, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency released nearly nine years ago.
There were zero commits and zero active maintainers in the last three months, consistent with the last push occurring in 2017. This leaves compatibility and maintenance risk unresolved.
The repository name does not match the package name and its README does not mention the package. Although subpackages can use different repository names, this combination makes the package-to-source relationship unclear.
The repository is not marked archived, but its last push was in August 2017; the observed inactivity matters more than the administrative archive status.
The release declares BSD-3-Clause but contains an MIT license file, creating a licensing mismatch despite having a license file and repository license.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version 2.* | — | — |
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.