The project is small, with three stars, two forks, one open issue, and no automated security tooling. Its MIT declaration, Composer build, stable v1.0.0 release, and matching repository provide useful transparency, but do not offset the maintenance risk.
43%
Total Score
50
100
83
83
One registry maintainer is consistent with the repository being owned by an individual, but it leaves little visible maintainer redundancy.
The registry namespace and repository are owned by the same individual, providing consistent ownership context but no organizational backing to compensate for the thin maintainer base.
The latest release was in February 2016, with no releases in the last 12 months; this is a substantial abandonment concern despite the package having two historical releases.
There were zero commits and zero active maintainers in the last three months, strongly indicating that the repository is no longer actively maintained.
One open issue and no issue or pull-request activity in the last month provide no evidence of current community or maintainer response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
joshdifabio/magento1-composer-bridge Version ~1.0-alpha1 | — | — |
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.