Clear documentation, licensing, type declarations, and release notes support adoption. The project shows strong ongoing activity and build provenance; its workflow permissions and repository-package linkage merit extra care.
88%
Total Score
100
94
83
100
The repository name does not match the package and its README does not mention the package, so the exact package-to-source relationship is less transparent. The organization-owned monorepo context partly explains the name mismatch but does not remove the missing mention.
All 12 workflows were analyzed with no unpinned actions, and 11 use read-only permissions. High-confidence findings that app tokens inherit blanket installation permissions, plus one top-level write-permission workflow, create a real workflow-hygiene caution; the template-injection finding is not paired with an untrusted checkout or script-injection trigger.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-833155 @ai-sdk/harness-codex is vulnerable to Authorization Bypass in versions 1.0.12 - 1.0.28. | 1.0.12 - 1.0.28 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
ws Version ^8.21.0 | — | — |
@ai-sdk/harness Version 1.0.122 | — | — |
@ai-sdk/provider-utils Version 5.0.46 | — | — |
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.