Leaderboard github.com
isohuntto/openbay
AI provenance
0%
none-detected
- Confidence
- 42%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
60/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
69/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.00
Lines added per month all AI-attributed share
- 2015-029,896 · 0% AI
- 2015-030 · 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
- 6
- effective_loc
- 9,896
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 9,792
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 14
- measured_loc
- 104
- median_loc_per_hour
- 0
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 104
- work_units
- 2
Release velocityskipped
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0
- lines_scanned
- 8,413
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
60 weak
Code quality is weak: test-to-source ratio 0.17, no CI test run detected; 2% of function code in complex or long functions; 22% duplicated lines. Weakest area: duplication.
How the score is built
- Complexity94
- Duplication26
- Lint and smells82
- Tests and CI38
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok1 item
- complex_functions
- 1
- function_nloc
- 2,915
- functions
- 345
- long_functions
- 0
- many_param_functions
- 0
- mean_ccn
- 2.01
- p90_ccn
- 4
- risky_nloc_share
- 1.9%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: backend/assets/AppAsset.php:13 and frontend/assets/AppAsset.php:13
- 6+ duplicated lines: backend/config/main.php:16 and frontend/config/main.php:63
- 6+ duplicated lines: backend/controllers/SiteController.php:30 and frontend/controllers/SiteController.php:39
- 6+ duplicated lines: backend/views/layouts/main.php:1 and frontend/views/layouts/main.php:1
- 6+ duplicated lines: backend/views/site/error.php:1 and frontend/views/site/error.php:1
- 6+ duplicated lines: backend/views/site/index.php:19 and backend/views/site/index.php:29
- 6+ duplicated lines: backend/views/site/login.php:1 and frontend/views/site/login.php:1
- 6+ duplicated lines: common/models/torrent/Files.php:33 and common/models/torrent/Scrape.php:39
- 6+ duplicated lines: common/modules/torrent_scraper/models/QueueProcessor.php:40 and common/modules/torrent_scraper/models/QueueProcessor.php:141
- 6+ duplicated lines: console/config/main.php:1 and environments/prod/console/config/main-local.php:1
- compared_lines
- 5,131
- duplicated_lines
- 1,146
- duplicated_share
- 22.3%
- files
- 180
Lintok
- category:best-practice
- 6
- category:correctness
- 3
- findings
- 9
- scanned_lines
- 8,413
- weighted_findings
- 6.75
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- yes
- ci_files
- 0
- cochange_commits
- 3
- cochange_share
- 33.3%
- source_lines
- 8,413
- test_lines
- 1,394
- test_ratio
- 0.17
Documentationok2 items
- README.md
README.md - LICENSE.md
LICENSE.md
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 185
Type safetyskipped
Security
69 weak
Security posture is weak: 4 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets90
- Static analysis (SAST)77
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 3
Static analysis (opengrep)ok
- findings
- 14
- findings_high
- 4
- findings_low
- 1
- findings_medium
- 9
- parse_errors
- 0
- scanned_lines
- 8,413
- weighted_findings
- 6.36
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- composer.json has no lockfile alongside it (unpinned dependencies)
composer.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 1
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
4 high15 medium7 low
26 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/php.lang.security.weak-crypto |
frontend/modules/comment/components/Utils.php:11 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
frontend/modules/complain/components/Utils.php:11 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
frontend/modules/rating/components/Utils.php:11 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.mcrypt-use |
init:190 | Mcrypt functionality has been deprecated and/or removed in recent PHP versions. Consider using Sodium or OpenSSL. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
frontend/modules/comment/assets/js/comments.js:23 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
frontend/modules/comment/assets/js/comments.js:26 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
frontend/modules/complain/assets/js/complain.js:5 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
frontend/modules/complain/assets/js/complain.js:7 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
frontend/modules/rating/assets/js/rating.js:11 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
frontend/modules/rating/assets/js/rating.js:8 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/php.symfony.security.audit.symfony-non-literal-redirect |
frontend/modules/search/controllers/DefaultController.php:34 | The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an... | Static analysis (opengrep) |
| medium | opengrep/php.symfony.security.audit.symfony-non-literal-redirect |
frontend/modules/search/controllers/DefaultController.php:83 | The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
frontend/modules/torrent/assets/src/js/rating.js:11 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
frontend/modules/torrent/assets/src/js/rating.js:11 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.symfony.security.audit.symfony-non-literal-redirect |
frontend/modules/torrent/controllers/DefaultController.php:73 | The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-assignment |
frontend/themes/newopb/assets/js/ui.js:29 | Possibility of prototype polluting assignment detected. By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.detect-eval-with-expression |
frontend/themes/newopb/assets/js/ui.js:29 | Detected use of dynamic execution of JavaScript which may come from user-input, which can lead to Cross-Site-Scripting (XSS). Where possible avoid including user-input in functions which dynamically execute user-input. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.detect-eval-with-expression |
frontend/themes/newopb/assets/js/ui.js:29 | Detected use of dynamic execution of JavaScript which may come from user-input, which can lead to Cross-Site-Scripting (XSS). Where possible avoid including user-input in functions which dynamically execute user-input. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.detect-eval-with-expression |
frontend/themes/newopb/assets/js/ui.js:29 | Detected use of dynamic execution of JavaScript which may come from user-input, which can lead to Cross-Site-Scripting (XSS). Where possible avoid including user-input in functions which dynamically execute user-input. [confidence medium] | Static analysis (opengrep) |
| low | opengrep/javascript.lang.correctness.useless-assignment |
frontend/themes/newopb/assets/js/ui.js:29 | `i` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
frontend/themes/newopb/assets/js/ui.js:29 | `e` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
frontend/themes/newopb/assets/js/ui.js:29 | `r` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.browser.security.js-open-redirect-from-function |
frontend/themes/newopb/assets/js/ui.js:29 | The application accepts potentially user-controlled input `e` which can control the location of the current window context. This can lead two types of vulnerabilities open-redirection and Cross-Site-Scripting (XSS) with JavaScript URIs.... | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
tests/codeception/common/fixtures/data/init_login.php:6 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
tests/codeception/common/unit/fixtures/data/models/user.php:6 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
tests/codeception/frontend/unit/fixtures/data/models/user.php:6 | 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 | 9 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 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 | skipped | — | 0 | no registry dependencies declared |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 14 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 3 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 53bddc618d6e | prov-5+qual-2+sec-2 | 0% | 60 | 69 |
| 2026-11-14 | 53bddc618d6e | prov-4+qual-2+sec-2 | 0% | 60 | 69 |
Full text report
- Repository: https://github.com/isohuntto/openbay
- Commit:
53bddc618d6e2bd6f266d2a58b5c5e37de4a692f - Generated: 2026-11-14T14:52:05+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 | none-detected | 42% | 100% |
| Code quality | 60 | weak | 90% | 100% |
| Security | 69 | weak | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
- Explicitly attributed share (lower bound): 0.0%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 0.0%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2015-02 | 9,896 | 0% |
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.17, no CI test run detected; 2% of function code in complex or long functions; 22% duplicated lines. Weakest area: duplication.
| Area | Score |
|---|---|
| Complexity (lizard) | 94 |
| Duplication | 26 |
| Code smells (Opengrep) | 82 |
| Tests and CI | 38 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 345; mean complexity 2.0, 90th percentile 4; 1 complex and 0 long functions
- Duplicated lines: 22.3% of 5,131 compared
- Tests: 1,394 test lines for 8,413 source lines (ratio 0.17); CI test commands: none detected; 33% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
Security
Security posture is weak: 4 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 90 |
| Static analysis (Opengrep) | 77 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
frontend/modules/comment/components/Utils.php:11 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
frontend/modules/complain/components/Utils.php:11 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
frontend/modules/rating/components/Utils.php:11 |
| high | opengrep/php.lang.security.mcrypt-use: Mcrypt functionality has been deprecated and/or removed in recent PHP versions. Consider using Sodium or OpenSSL. [confidence low] |
init:190 |
| medium | opengrep/php.symfony.security.audit.symfony-non-literal-redirect: The redirect() method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. [confidence low] |
frontend/modules/search/controllers/DefaultController.php:34 |
| medium | opengrep/php.symfony.security.audit.symfony-non-literal-redirect: The redirect() method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. [confidence low] |
frontend/modules/search/controllers/DefaultController.php:83 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
frontend/modules/torrent/assets/src/js/rating.js:11 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
frontend/modules/torrent/assets/src/js/rating.js:11 |
| medium | opengrep/php.symfony.security.audit.symfony-non-literal-redirect: The redirect() method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. [confidence low] |
frontend/modules/torrent/controllers/DefaultController.php:73 |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-assignment: Possibility of prototype polluting assignment detected. By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the software depends on existence or non-ex [confidence low] |
frontend/themes/newopb/assets/js/ui.js:29 |
| medium | opengrep/javascript.lang.security.detect-eval-with-expression: Detected use of dynamic execution of JavaScript which may come from user-input, which can lead to Cross-Site-Scripting (XSS). Where possible avoid including user-input in functions which dynamically execute user-input. [confidence medium] |
frontend/themes/newopb/assets/js/ui.js:29 |
| medium | opengrep/javascript.lang.security.detect-eval-with-expression: Detected use of dynamic execution of JavaScript which may come from user-input, which can lead to Cross-Site-Scripting (XSS). Where possible avoid including user-input in functions which dynamically execute user-input. [confidence medium] |
frontend/themes/newopb/assets/js/ui.js:29 |
| medium | opengrep/javascript.lang.security.detect-eval-with-expression: Detected use of dynamic execution of JavaScript which may come from user-input, which can lead to Cross-Site-Scripting (XSS). Where possible avoid including user-input in functions which dynamically execute user-input. [confidence medium] |
frontend/themes/newopb/assets/js/ui.js:29 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
tests/codeception/common/fixtures/data/init_login.php:6 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
tests/codeception/common/unit/fixtures/data/models/user.php:6 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
tests/codeception/frontend/unit/fixtures/data/models/user.php:6 |
| low | opengrep/javascript.browser.security.js-open-redirect-from-function: The application accepts potentially user-controlled input e which can control the location of the current window context. This can lead two types of vulnerabilities open-redirection and Cross-Site-Scripting (XSS) with JavaScript URIs. It is recommended to validate user-controllable input before al [confidence low] |
frontend/themes/newopb/assets/js/ui.js:29 |
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.
Repository profile
- Source lines: 8,413; test lines: 1,394
| Language | Lines |
|---|---|
| PHP | 9,678 |
| JavaScript | 129 |