The license, README, and Composer-only runtime profile are clear. Single-person ownership and the repository’s failure to identify or mention this package limit confidence for a core B2B dependency.
54%
Total Score
50
100
72
75
Only one registry publishing account is listed. That can be sufficient for a small project, but it leaves limited observable publishing redundancy.
The repository is owned by an individual user rather than an organization, so the single-person maintainer picture is not compensated by visible organizational backing.
There are only two releases across 103 days, with both releases clustered about 2 hours and 26 minutes apart; this provides limited evidence of a sustained release process.
The repository recorded zero commits and zero active maintainers during the last three months. For a package only 103 days old, this leaves maintenance continuity uncertain.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked source repository is specifically the package’s maintained home.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
orangecat/core Version * | — | — |
magento/framework Version >=103.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.