Leaderboard github.com
SteamedFish/opencode-guard
An opencode plugin to protect your passwords and tokens
AI provenance
0%
possible
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
65/100
adequate
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
68/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% possible
Weak signals consistent with AI-assisted development.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts73%
- Estimated AI-generated share0%
- AI tool configuration files1
- Work sessions at AI pace3
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.18
Lines added per month all AI-attributed share
- 2026-036,045 · 0% AI
- 2026-096,815 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 106
- effective_loc
- 12,860
- tools_detected
- 0
AI tool configurationok1 item
- artifacts
- 1
- earliest_adoption
- 2026-03-29
- tools_configured
- 1
- workflow_agents
- 0
Commit velocityok3 items
- 3,999 lines of first-party code in ~6.8h (592 lines/hour, 8 commit session)
- 2,817 lines of first-party code in ~4.9h (576 lines/hour, 10 commit session)
- 2,589 lines of first-party code in ~4.8h (534 lines/hour, 11 commit session)
- excluded_import_loc
- 0
- flagged_loc
- 9,405
- flagged_loc_share
- 73.1%
- flagged_units
- 3
- max_loc_per_hour
- 591.57
- measured_loc
- 12,860
- median_loc_per_hour
- 192.32
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 13
Release velocityskipped
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 2
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 2
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0.18
- lines_scanned
- 5,413
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0.37
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
65 adequate
Code quality is adequate: test-to-source ratio 1.17, no CI test run detected; 26% of function code in complex or long functions; 1% duplicated lines. Weakest area: type safety.
How the score is built
- Complexity46
- Duplication91
- Lint and smells91
- Tests and CI55
- Documentation65
- Type safety40
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- build_response in scripts/e2e/capture-server.py: complexity 43, 80 lines
- (anonymous) in src/index.js: complexity 35, 58 lines
- main in scripts/e2e/verify-probe.py: complexity 29, 116 lines
- detectSensitiveData in src/detector.js: complexity 29, 84 lines
- loadConfig in src/config.js: complexity 26, 72 lines
- maskRequest in src/v2.js: complexity 26, 52 lines
- buildPatternSet in src/patterns.js: complexity 24, 58 lines
- flushChoiceRemainders in src/response-unmasker.js: complexity 20, 46 lines
- dispatchEvent in src/response-unmasker.js: complexity 20, 50 lines
- isExcludedMcpTool in src/guard-core.js: complexity 19, 18 lines
- complex_functions
- 15
- function_nloc
- 3,260
- functions
- 264
- long_functions
- 1
- many_param_functions
- 0
- mean_ccn
- 4.80
- p90_ccn
- 10
- risky_nloc_share
- 25.9%
Duplication (jscpd)ok4 items
- 6+ duplicated lines: scripts/e2e/capture-server.py:116 and scripts/e2e/capture-server.py:481
- 6+ duplicated lines: src/ai-detector/providers/custom.js:48 and src/ai-detector/providers/openai.js:41
- 6+ duplicated lines: src/engine.js:82 and src/restore.js:104
- 6+ duplicated lines: src/response-unmasker.js:60 and src/streaming-unmasker.js:75
- compared_lines
- 3,893
- duplicated_lines
- 58
- duplicated_share
- 1.5%
- files
- 36
Lintok
- category:correctness
- 2
- findings
- 2
- scanned_lines
- 5,413
- weighted_findings
- 2
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- yes
- check:tests_cochange
- yes
- ci_files
- 0
- cochange_commits
- 52
- cochange_share
- 57.7%
- source_lines
- 5,413
- test_lines
- 6,347
- test_ratio
- 1.17
Documentationok2 items
- README.md
README.md - LICENSE
LICENSE
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 163
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 0
- escapes_per_kloc
- 0
Security
68 weak
Security posture is weak: 1 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets72
- Static analysis (SAST)88
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture20
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 1
- declared
- 1
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 1
- secrets_nonprod
- 9
Static analysis (opengrep)ok
- findings
- 6
- findings_high
- 1
- findings_low
- 0
- findings_medium
- 5
- parse_errors
- 0
- scanned_lines
- 5,413
- weighted_findings
- 2
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- package.json has no lockfile alongside it (unpinned dependencies)
package.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- yes
- signed_commit_share
- 100.0%
- unpinned_manifests
- 1
Release downloadsok2 items
- gives an archive password
README.md - gives an archive password
README.zh-CN.md
- binary_assets
- 0
- signals
- 1
- suspicious
- 0
Findings
1 high7 medium10 low
18 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/javascript.lang.security.detect-child-process |
src/ai-detector/auto-install.js:54 | Detected calls to child_process from a function argument `packageName`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
src/ai-detector/providers/custom.js:49 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
src/ai-detector/providers/openai.js:42 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
src/maskers/custom.js:87 | RegExp() called with a `config` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-redos |
src/maskers/ip.js:89 | Detected the use of a regular expression... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
src/patterns.js:56 | RegExp() called with a `patterns` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
src/patterns.js:73 | RegExp() called with a `patterns` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
src/streaming-unmasker.js:110 | RegExp() called with a `keys` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
docs/AI_DETECTION_PLAN.md:327 | Possible generic-api-key secret in history (commit 5507cd491c); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
docs/plan.md:2242 | Possible generic-api-key secret in history (commit 983052d14b); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
plan/AI_DETECTION_PLAN.md:327 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
plan/plan.md:2242 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
scripts/e2e/fake-mcp-server.py:28 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
tests/ai-detector/local.test.js:31 | Possible generic-api-key secret in history (commit 5507cd491c); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/github-pat |
tests/edge-cases.test.js:266 | Possible github-pat secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
tests/maskers/credential.test.js:50 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
tests/response-unmasker.test.js:56 | Possible generic-api-key secret in history (commit e3a9b8ded0); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
tests/streaming-unmasker.test.js:8 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 2 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 6 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 10 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 0e1b03cfdd7d | prov-5+qual-2+sec-2 | 0% | 65 | 68 |
| 2026-11-14 | 0e1b03cfdd7d | prov-4+qual-2+sec-2 | 0% | 65 | 68 |
Full text report
- Repository: https://github.com/SteamedFish/opencode-guard
- Commit:
0e1b03cfdd7de3fccabea35b54a16288eb73c72e - Generated: 2026-11-14T14:52:01+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | possible | 65% | 100% |
| Code quality | 65 | adequate | 90% | 100% |
| Security | 68 | weak | 85% | 100% |
AI provenance
Weak signals consistent with AI-assisted development.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 73.1%
-
Estimated AI-generated share: 0.0%
-
AI tooling configured in repo: generic-agent
-
Stylometry index: 0.18 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 0, emoji 2). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2026-03 | 6,045 | 0% |
| 2026-09 | 6,815 | 0% |
Evidence
- AGENTS.md (generic-agent configuration) (AGENTS.md)
- 3,999 lines of first-party code in ~6.8h (592 lines/hour, 8 commit session) (307b7b9b2853)
- 2,817 lines of first-party code in ~4.9h (576 lines/hour, 10 commit session) (311d1ecc9080)
- 2,589 lines of first-party code in ~4.8h (534 lines/hour, 11 commit session) (7a33938d626e)
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 adequate: test-to-source ratio 1.17, no CI test run detected; 26% of function code in complex or long functions; 1% duplicated lines. Weakest area: type safety.
| Area | Score |
|---|---|
| Complexity (lizard) | 46 |
| Duplication | 91 |
| Code smells (Opengrep) | 91 |
| Tests and CI | 55 |
| Documentation | 65 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 264; mean complexity 4.8, 90th percentile 10; 15 complex and 1 long functions
- Duplicated lines: 1.5% of 3,893 compared
- Tests: 6,347 test lines for 5,413 source lines (ratio 1.17); CI test commands: none detected; 58% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- build_response in scripts/e2e/capture-server.py: complexity 43, 80 lines
- (anonymous) in src/index.js: complexity 35, 58 lines
- main in scripts/e2e/verify-probe.py: complexity 29, 116 lines
- detectSensitiveData in src/detector.js: complexity 29, 84 lines
- loadConfig in src/config.js: complexity 26, 72 lines
Security
Security posture is weak: 1 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 72 |
| Static analysis (Opengrep) | 88 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 20 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: signed commits; missing: security policy, dependency updates, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument packageName. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
src/ai-detector/auto-install.js:54 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a config function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controll [confidence low] |
src/maskers/custom.js:87 |
| medium | opengrep/javascript.lang.security.audit.detect-redos: Detected the use of a regular expression `^(?:[0-9a-fA-F]{1,4}:){7}[0-9a-fA-F]{1,4}$|^(?:[0-9a-fA-F]{1,4}:){1,7}:$|^(?:[0-9a-fA-F]{1,4}:){1,6}:[0-9a-fA-F]{1,4}$|^(?:[0-9a-fA-F]{1,4}:){1,5}(?::[0-9a-fA-F]{1,4}){1,2}$|^(?:[0-9a-fA-F]{1,4}:){1,4}(?::[0-9a-fA-F]{1,4}){1,3}$|^(?:[0-9a-fA-F]{1,4}:){1,3}(? [confidence low] |
src/maskers/ip.js:89 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a patterns function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-contro [confidence low] |
src/patterns.js:56 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a patterns function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-contro [confidence low] |
src/patterns.js:73 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a keys function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled [confidence low] |
src/streaming-unmasker.js:110 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
scripts/e2e/fake-mcp-server.py:28 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
tests/maskers/credential.test.js:50 |
| low | gitleaks/github-pat: Possible github-pat secret in the current tree (test/docs/example file) |
tests/edge-cases.test.js:266 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
tests/streaming-unmasker.test.js:8 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
plan/AI_DETECTION_PLAN.md:327 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
plan/plan.md:2242 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit e3a9b8ded0); removed from the current tree but still retrievable |
tests/response-unmasker.test.js:56 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 5507cd491c); removed from the current tree but still retrievable |
tests/ai-detector/local.test.js:31 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 983052d14b); removed from the current tree but still retrievable |
docs/plan.md:2242 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 5507cd491c); removed from the current tree but still retrievable |
docs/AI_DETECTION_PLAN.md:327 |
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
- readme-download-lure: gives an archive password
- readme-download-lure: gives an archive password
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
- Source lines: 5,413; test lines: 6,347
| Language | Lines |
|---|---|
| JavaScript | 10,828 |
| Python | 932 |