The package has a clear README, a declared license, and no install-time scripts. Its release and commit activity stopped over 10 years ago, with little repository adoption and no security policy or scanning. Pin this only when maintaining the legacy PHP integration is acceptable.
42%
Total Score
33
100
72
67
The package has made no releases in the last 12 months, and its latest release was published in January 2016. This is strong evidence of abandonment risk for a library dependency.
There were no commits and no active maintainers in the last three months, consistent with the repository having been inactive since 2016. This is the strongest maintenance and abandonment concern.
Only one registry account has publishing access. That is a narrow publishing base for an independently backed project and increases continuity risk when combined with the absence of recent activity.
The package and repository contain only five files, including a README and Composer metadata but no tests or dedicated documentation beyond the README. This is a thin project structure and limits transparency into long-term maintenance.
The package and repository are owned by the same individual account, with no organization backing shown. This is consistent ownership but provides limited evidence of maintenance capacity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
j4mie/idiorm Version 1.5.1 | — | — |
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.