55%
Total Score
caution
Extremely rapid releases, a postinstall binary installer, and heavy prerelease use make this release worth adopting cautiously.
A postinstall script runs during installation, increasing dependency-installation complexity and the consequences of a compromised or broken release.
No build attestation is present, so consumers cannot independently verify how the published binary was produced. Trusted publisher identity is present, but it does not replace artifact provenance.
The four-file artifact is a platform-binary wrapper containing LICENSE, package.json, postinstall.mjs, and a Windows executable; this is a coherent CLI packaging shape but provides little transparency in the artifact itself.
The published artifact has no README, tests, changelog, or release notes. Tests and changelogs normally belong in source repositories, but the missing README reduces usability for a CLI package.
The package is mature at 498 days old and has extensive release activity, but 10,498 releases in the last 12 months with a median interval of about 23 minutes is unusually rapid and makes release selection harder to audit.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-260577 opencode-ai is vulnerable to Missing Authentication in versions 0.0.1 - 1.0.215. | 0.0.1 - 1.0.215 | High |
AIKIDO-2026-10027 opencode-ai is vulnerable to Remote Code Execution (RCE) in versions 0.0.1 - 1.1.9. | 0.0.1 - 1.1.9 | Critical |
No direct dependencies.
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.