The matching repository and stable version reduce uncertainty, but the project has had no release or commit activity for more than three years. Install-time scripts, no tests, and no security scanning add maintenance and supply-chain concerns.
38%
Total Score
0
79
50
The latest release was over three years ago, with no releases in the last 12 months and only three releases overall. The very short early release interval does not compensate for the prolonged inactivity.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the extended release gap and indicating little current maintenance capacity.
The package runs post-install and post-update Composer scripts, increasing the amount of package code executed during dependency operations. No provided signal shows these scripts are unsafe, so this is a maintenance and supply-chain caution rather than a verdict on the package.
Composer build tooling is present, but no security scanning tools were detected. That leaves an avoidable gap in ongoing dependency and source checks for a package that runs lifecycle scripts.
The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled. This matters more alongside the absence of recent maintenance activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
orchid/platform Version ^13.9 | — | — |
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.