70%
Total Score
caution
Active, well-documented releases are offset by risky workflow findings and weak evidence tying the package to its repository.
The repository name does not match the package and its README does not mention @ai-sdk/harness; this can be normal for a monorepo subpackage, but it weakens direct package-to-repository traceability.
All 13 workflows were analyzed with no failed files and all 78 action references pinned, but high-confidence blanket GitHub App permissions and template injection in a workflow_run workflow, plus an untrusted checkout in another workflow_run workflow, create meaningful automation risk; the repeated cache findings are low confidence and carry little weight.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-934633 New @ai-sdk/harness is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 1.0.0 - 1.0.132. | 1.0.0 - 1.0.132 | High |
| Dependency | Last Release | Score |
|---|---|---|
ai Version 7.0.130 | — | — |
@ai-sdk/provider Version 4.0.24 | — | — |
@ai-sdk/provider-utils Version 5.0.56 | — | — |
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.