RepoTrust

iFurySt/open-computer-use

👾 Open Computer Use – Open-Source Alternative to Codex Computer Use

https://github.com/iFurySt/open-computer-use · commit e25be21caa0e · scored 2026-11-14 · scoring prov-4+qual-2+sec-2

RepoTrust ai badge RepoTrust quality badge RepoTrust security badge

Dispute this score or request a re-score Full report JSON

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 10 explicit 95% 100%
Code quality 62 weak 90% 100%
Security 79 adequate 85% 100%

AI provenance

Explicit AI attribution on 10% of first-party code added; an estimated 10% including velocity signals.

AI tool Attributed commits Lines added
OpenAI Codex 26 7,123
Claude Code 7 598

Current source lines last changed by AI-attributed commits: 4,126 of 58,251.

Findings per 1,000 lines AI-attributed Other Ratio
Quality 0.727 0.794 0.92x
Security 0.969 0.277 3.5x
Month Lines added Attributed to AI
2026-04 32,770 2%
2026-05 3,729 19%
2026-06 2,166 1%
2026-07 2,221 0%
2026-08 186 0%
2026-09 3,269 5%
2026-10 24,505 19%
2026-11 7,483 20%

Evidence

AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.

Code quality

Code quality is weak: test-to-source ratio 0.19, CI runs tests; 18% of function code in complex or long functions; 14% duplicated lines. Weakest area: type safety.

Area Score
Complexity (lizard) 58
Duplication 43
Code smells (Opengrep) 76
Tests and CI 74
Documentation 80
Type safety 0
Process (Scorecard review/maintenance) n/a

Most complex functions:

Security

Security posture is adequate: 18 high-severity SAST findings; 6 high-severity workflow issues. Weakest area: ci actions.

Area Score
Secrets (gitleaks, tree + history) 94
Static analysis (Opengrep) 90
Vulnerable dependencies (OSV) 100
CI workflows (zizmor) 40
Posture (policy, updates, signing, lockfiles) 40
OpenSSF Scorecard n/a

Top findings

Severity Finding Location
high opengrep/go.lang.security.audit.dangerous-exec-command: Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. [confidence low] scripts/computer-use-cli/app_server.go:141
high opengrep/go.lang.security.audit.dangerous-exec-command: Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. [confidence low] scripts/computer-use-cli/main.go:359
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-native-validation.py:27
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-native-validation.py:72
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-native-validation.py:151
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-native-validation.py:182
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-native-validation.py:194
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-rehearsal.py:21
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-rehearsal.py:24
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-rehearsal.py:57
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-rehearsal.py:75
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-smoke.py:65
high opengrep/python.lang.security.audit.dangerous-subprocess-use-tainted-env-args: Detected subprocess function 'Popen' with user controlled data. A malicious actor could leverage this to perform command injection. You may consider using 'shlex.quote()'. [confidence medium] scripts/run-locked-use-smoke.py:65
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-smoke.py:79
high opengrep/python.lang.security.audit.dangerous-subprocess-use-tainted-env-args: Detected subprocess function 'run' with user controlled data. A malicious actor could leverage this to perform command injection. You may consider using 'shlex.quote()'. [confidence medium] scripts/run-locked-use-smoke.py:79
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-unshielded-diagnostic.py:37
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-unshielded-diagnostic.py:48
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] scripts/run-locked-use-unshielded-diagnostic.py:55
high zizmor/excessive-permissions: overly broad permissions [confidence high] .github/workflows/release.yml:22
high zizmor/excessive-permissions: overly broad permissions [confidence high] .github/workflows/release.yml:23
high zizmor/excessive-permissions: overly broad permissions [confidence high] .github/workflows/release.yml:24
high zizmor/cache-poisoning: runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] .github/workflows/release.yml:35
high zizmor/cache-poisoning: runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] .github/workflows/release.yml:54
high zizmor/cache-poisoning: runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] .github/workflows/release.yml:59
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] packages/LockedUseNative/PeerIdentity.c:16

Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.

Distribution signals

Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.

Repository profile

Language Lines
Swift 40,028
Go 7,461
Python 7,058
JavaScript 5,937
PowerShell 4,389
Shell 3,365
C 415
Objective-C 379

Embed a badge

Maintainers can show these in a README. Badges update when the repository is re-scored.

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/iFurySt/open-computer-use/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/iFurySt/open-computer-use/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/iFurySt/open-computer-use/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/iFurySt/open-computer-use/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/iFurySt/open-computer-use/security.svg)](https://repotrust.synapticcyber.com/r/github.com/iFurySt/open-computer-use/)