Leaderboard github.com
MPOS/php-mpos
MPOS stands for Mining Portal Open Source. Issue tracker is now closed since it's not maintained anymore.
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
57/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
60/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 pace0
- Coding-style index (1.0+ means possible)0.16
Lines added per month all AI-attributed share
- 2013-0555,879 · 0% AI
- 2013-068,702 · 0% AI
- 2013-074,157 · 0% AI
- 2013-082,313 · 0% AI
- 2013-0937,068 · 0% AI
- 2013-102,218 · 0% AI
- 2013-111,682 · 0% AI
- 2013-125,468 · 0% AI
- 2014-0115,595 · 0% AI
- 2014-0247,462 · 0% AI
- 2014-0345,183 · 0% AI
- 2014-04967 · 0% AI
- 2014-052,497 · 0% AI
- 2014-06393 · 0% AI
- 2014-07368 · 0% AI
- 2014-081,290 · 0% AI
- 2014-093 · 0% AI
- 2014-101 · 0% AI
- 2014-1114 · 0% AI
- 2014-122,354 · 0% AI
- 2015-0137 · 0% AI
- 2015-04930 · 0% AI
- 2015-0528 · 0% AI
- 2015-06309 · 0% AI
- 2015-0742 · 0% AI
- 2015-080 · 0% AI
- 2015-091 · 0% AI
- 2015-100 · 0% AI
- 2015-1214 · 0% AI
- 2016-015 · 0% AI
- 2016-028 · 0% AI
- 2016-032 · 0% AI
- 2016-050 · 0% AI
- 2016-06581 · 0% AI
- 2016-0761 · 0% AI
- 2017-01520 · 0% AI
- 2017-021 · 0% AI
- 2017-074 · 0% AI
- 2017-081 · 0% AI
- 2017-0968 · 0% AI
- 2017-100 · 0% AI
- 2017-111 · 0% AI
- 2017-12143 · 0% AI
- 2018-012 · 0% AI
- 2018-02119 · 0% AI
- 2018-03101 · 0% AI
- 2018-0453 · 0% AI
- 2018-0590 · 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
- 2,987
- effective_loc
- 236,735
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 81,109
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 5,600.50
- measured_loc
- 89,970
- median_loc_per_hour
- 51.00
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 49,232
- pre_ai_era_bursts
- 5
- pre_ai_era_measured_loc
- 89,970
- work_units
- 1,005
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 69.40
- releases
- 10
Coding styleok8 items
- step-by-step narration comment: // Now we can set our additional key prefix
- step-by-step narration comment: * Finally, a light, permissions-checking logging class.
- step-by-step narration comment: # First, look for nested blocks, e.g.:
- step-by-step narration comment: # First, handle reference-style links: [link text] [id]
- step-by-step narration comment: # Next, inline-style links: [link text](url "optional title")
- step-by-step narration comment: # First, handle reference-style labeled images: ![alt text][id]
- step-by-step narration comment: # Next, handle inline images: 
- step-by-step narration comment: # First, handle reference-style links: [link text] [id]
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 11
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 3
- files:placeholder
- 0
- index
- 0.16
- lines_scanned
- 70,300
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.16
- per_kloc:placeholder
- 0
Code quality
57 weak
Code quality is weak: test-to-source ratio 0.03, no CI test run detected; 21% of function code in complex or long functions; 13% duplicated lines. Weakest area: process.
How the score is built
- Complexity53
- Duplication45
- Lint and smells94
- Tests and CI37
- Documentation100
- Type safetynot measured
- Review process35
Evidence by analyzer
Complexity (lizard)ok10 items
- smarty_function_html_select_time in include/smarty/libs/plugins/function.html_select_time.php: complexity 134, 282 lines
- smarty_function_html_select_date in include/smarty/libs/plugins/function.html_select_date.php: complexity 126, 280 lines
- Smarty_Internal_Utility::testInstall in include/smarty/libs/sysplugins/smarty_internal_utility.php: complexity 91, 483 lines
- Mobile_Detect::mobileGrade in include/lib/Mobile_Detect.php: complexity 75, 52 lines
- (anonymous) in public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js: complexity 58, 11 lines
- smarty_function_fetch in include/smarty/libs/plugins/function.fetch.php: complexity 55, 175 lines
- Smarty_Resource::buildFilepath in include/smarty/libs/sysplugins/smarty_resource.php: complexity 37, 107 lines
- Share::findUpstreamShare in include/classes/share.class.php: complexity 36, 64 lines
- Fa in public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js: complexity 36, 5 lines
- smarty_function_html_checkboxes in include/smarty/libs/plugins/function.html_checkboxes.php: complexity 35, 104 lines
- complex_functions
- 60
- function_nloc
- 23,506
- functions
- 2,594
- long_functions
- 14
- many_param_functions
- 0
- mean_ccn
- 3.29
- p90_ccn
- 7
- risky_nloc_share
- 21.2%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: cronjobs/blockupdate.php:1 and cronjobs/findblock.php:1
- 6+ duplicated lines: cronjobs/blockupdate.php:2 and cronjobs/cron_end.inc.php:1
- 6+ duplicated lines: cronjobs/payouts.php:44 and cronjobs/payouts.php:131
- 6+ duplicated lines: cronjobs/pplns_payout.php:18 and cronjobs/pps_payout.php:18
- 6+ duplicated lines: cronjobs/pplns_payout.php:65 and cronjobs/proportional_payout.php:57
- 6+ duplicated lines: cronjobs/run-crons.sh:6 and cronjobs/run-maintenance.sh:4
- 6+ duplicated lines: cronjobs/run-maintenance.sh:1 and cronjobs/run-payout.sh:1
- 6+ duplicated lines: cronjobs/run-maintenance.sh:42 and cronjobs/run-statistics.sh:42
- 6+ duplicated lines: cronjobs/shared.inc.php:21 and public/index.php:20
- 6+ duplicated lines: cronjobs/statistics.php:18 and cronjobs/tables_cleanup.php:18
- compared_lines
- 45,826
- duplicated_lines
- 6,143
- duplicated_share
- 13.4%
- files
- 504
Lintok
- category:best-practice
- 1
- category:correctness
- 71
- findings
- 72
- scanned_lines
- 70,082
- weighted_findings
- 18.75
Tests and CIok1 item
- CI config: .travis.yml
.travis.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 1
- cochange_commits
- 212
- cochange_share
- 0.0%
- source_lines
- 70,343
- test_lines
- 2,389
- test_ratio
- 0.03
Documentationok4 items
- README.md
README.md - LICENSE
LICENSE - CONTRIBUTING.md
CONTRIBUTING.md - CHANGELOG.md
CHANGELOG.md
- check:changelog
- yes
- check:contributing
- yes
- check:license
- yes
- check:readme
- yes
- readme_lines
- 135
Type safetyskipped
Security
60 weak
Security posture is weak: 84 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets94
- Static analysis (SAST)66
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecard25
Evidence by analyzer
OpenSSF Scorecardok9 items
- Scorecard Code-Review: 7/10 (Found 7/9 approved changesets -- score normalized to 7)
- Scorecard Maintained: 0/10 (0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0)
- Scorecard Binary-Artifacts: 10/10 (no binaries found in the repo)
- Scorecard CII-Best-Practices: 0/10 (no effort to earn an OpenSSF best practices badge detected)
- Scorecard Security-Policy: 0/10 (security policy file not detected)
- Scorecard Fuzzing: 0/10 (project is not fuzzed)
- Scorecard License: 10/10 (license file detected)
- Scorecard Branch-Protection: 0/10 (branch protection not enabled on development/release branches)
- Scorecard SAST: 0/10 (SAST tool is not run on all commits -- score normalized to 0)
- aggregate
- 3
- check:Binary-Artifacts
- yes
- check:Branch-Protection
- no
- check:CII-Best-Practices
- no
- check:Code-Review
- yes
- check:Fuzzing
- no
- check:License
- yes
- check:Maintained
- no
- check:SAST
- no
- check:Security-Policy
- no
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 1
- secrets_nonprod
- 1
Static analysis (opengrep)ok
- findings
- 124
- findings_high
- 84
- findings_low
- 0
- findings_medium
- 40
- parse_errors
- 0
- scanned_lines
- 70,082
- weighted_findings
- 83.85
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
- 18.0%
- unpinned_manifests
- 1
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
84 high41 medium73 low
198 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/php.lang.security.weak-crypto |
cronjobs/shared.inc.php:29 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/classes/memcache_ad.class.php:15 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/classes/memcache_ad.class.php:64 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/classes/user.class.php:637 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.md5-loose-equality |
include/classes/user.class.php:959 | Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
include/lib/jsonRPCClient.php:111 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php:420 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php:689 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php:85 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php:68 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php:78 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php:79 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.mcrypt-use |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:559 | Mcrypt functionality has been deprecated and/or removed in recent PHP versions. Consider using Sodium or OpenSSL. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.mcrypt-use |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:560 | Mcrypt functionality has been deprecated and/or removed in recent PHP versions. Consider using Sodium or OpenSSL. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.mcrypt-use |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:562 | Mcrypt functionality has been deprecated and/or removed in recent PHP versions. Consider using Sodium or OpenSSL. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:576 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:583 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
include/lib/swiftmailer/classes/Swift/Transport/StreamBuffer.php:292 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getdashboarddata.inc.php:121 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/gethourlyhashrates.inc.php:17 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getuserbalance.inc.php:11 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getuserhashrate.inc.php:21 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getusersharerate.inc.php:21 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getuserstatus.inc.php:27 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getusertransactions.inc.php:38 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
include/pages/api/getuserworkers.inc.php:14 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty.inc.php:18 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/Smarty.class.php:1235 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/SmartyBC.class.php:456 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/plugins/function.math.php:75 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/plugins/shared.literal_compiler_param.php:31 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_cacheresource_custom.php:135 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_cacheresource_custom.php:84 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_cacheresource_keyvaluestore.php:101 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_cacheresource_keyvaluestore.php:192 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_cacheresource_file.php:167 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_cacheresource_file.php:61 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_compile_extends.php:56 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_compile_function.php:69 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_compile_include.php:164 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_compile_include.php:168 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_compile_include_php.php:61 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_compile_insert.php:63 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_compile_insert.php:75 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_config.php:107 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_function_call_handler.php:48 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_resource_eval.php:32 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_resource_extends.php:53 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_resource_file.php:36 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_resource_php.php:46 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_resource_registered.php:32 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_resource_string.php:32 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_template.php:223 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_template.php:252 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_template.php:661 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_templatebase.php:141 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_templatebase.php:151 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_templatebase.php:165 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
include/smarty/libs/sysplugins/smarty_internal_templatebase.php:254 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_internal_utility.php:202 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
include/smarty/libs/sysplugins/smarty_resource_custom.php:52 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.file-inclusion |
public/index.php:145 | Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead,... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.file-inclusion |
public/index.php:148 | Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead,... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
public/index.php:28 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:22 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:22 | User controlled data in a `c.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:24 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:24 | User controlled data in a `i.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:45 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:45 | User controlled data in a `ua.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:58 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:58 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:58 | User controlled data in a `a.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:58 | User controlled data in a `a.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
scripts/shared.inc.php:34 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.1_to_0.0.2.inc.php:16 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.2_to_0.0.3.inc.php:20 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.3_to_0.0.4.inc.php:19 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.4_to_0.0.5.inc.php:17 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.5_to_0.0.6.inc.php:16 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.6_to_0.0.7.inc.php:16 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.9_to_0.0.10.inc.php:18 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
upgrade/definitions/0.0.9_to_0.0.10.inc.php:28 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
upgrade/shared.inc.php:34 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:74 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/php.lang.security.unserialize-use |
include/classes/usersettings.class.php:48 | Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/lib/swiftmailer/classes/Swift/ByteStream/TemporaryFileByteStream.php:41 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unserialize-use |
include/lib/swiftmailer/classes/Swift/FileSpool.php:168 | Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/lib/swiftmailer/classes/Swift/FileSpool.php:172 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/lib/swiftmailer/classes/Swift/KeyCache/DiskKeyCache.php:244 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
include/smarty/libs/plugins/function.html_image.php:123 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
include/smarty/libs/plugins/function.html_image.php:124 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
include/smarty/libs/plugins/function.html_image.php:128 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/smarty/libs/sysplugins/smarty_internal_cacheresource_file.php:227 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/smarty/libs/sysplugins/smarty_internal_cacheresource_file.php:275 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/smarty/libs/sysplugins/smarty_internal_utility.php:260 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/smarty/libs/sysplugins/smarty_internal_write_file.php:58 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
include/smarty/libs/sysplugins/smarty_internal_write_file.php:66 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
public/index.php:123 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/dataTables.bootstrap.js:7 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:109 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:119 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:139 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:156 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-loop |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:19 | Possibility of prototype polluting function 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... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-loop |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:19 | Possibility of prototype polluting function 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... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-loop |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:21 | Possibility of prototype polluting function 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... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:21 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:26 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:30 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:44 | RegExp() called with a `a` 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-non-literal-regexp |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:44 | RegExp() called with a `h` 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.incomplete-sanitization |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:44 | `a.replace` method will only replace the first occurrence when used with a string argument ('"'). If this method is used for escaping of dangerous data then there is a possibility for a bypass. Try to use sanitization library instead or... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:45 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:47 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:52 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:64 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:93 | RegExp() called with a `b` 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.jquery.security.audit.jquery-insecure-selector |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:104 | 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 |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:157 | 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 |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:225 | 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 |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:229 | 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 |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:270 | 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 |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:274 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
public/site_assets/bootstrap/js/plugins/metisMenu/jquery.metisMenu.js:352 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/logrotate.sh:10 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/logrotate.sh:5 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/logrotate.sh:5 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/logrotate.sh:7 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:109 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:120 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:127 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:131 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:49 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:72 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-crons.sh:75 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-crons.sh:75 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:75 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:76 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-crons.sh:82 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:82 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:84 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-crons.sh:88 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:120 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:126 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:137 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:144 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:148 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:47 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:79 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-maintenance.sh:82 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-maintenance.sh:82 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:82 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:83 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-maintenance.sh:89 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:89 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:91 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-maintenance.sh:95 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:119 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:125 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:136 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:143 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:147 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:47 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:78 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-payout.sh:81 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-payout.sh:81 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:81 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:82 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-payout.sh:88 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:88 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:90 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-payout.sh:94 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:120 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:126 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:137 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:144 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:148 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:47 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:79 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-statistics.sh:82 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-statistics.sh:82 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:82 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:83 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-command-substitution-in-command |
cronjobs/run-statistics.sh:89 | The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:89 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:91 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
cronjobs/run-statistics.sh:95 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:135 | `b` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:139 | `a` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:53 | `l` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:68 | `c` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:75 | `e` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:9 | `j` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:91 | `j` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js:92 | `j` is assigned twice; the first assignment is useless | Lint |
| low | gitleaks/generic-api-key |
README.md:18 | Possible generic-api-key secret in history (commit 73455c97e9); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
public/include/config/global.inc.dist.php:13 | Possible generic-api-key secret in history (commit b728b680ca); removed from the current tree but still retrievable | 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 | ok | prov-4 | 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 | 72 | |
| 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 | 124 | |
| OpenSSF Scorecard | Security | ok | scorecard v5.6.0 | 0 | |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 2 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 236cccd5d317 | prov-5+qual-2+sec-2 | 0% | 57 | 60 |
| 2026-11-14 | 236cccd5d317 | prov-4+qual-2+sec-2 | 0% | 57 | 60 |
Full text report
- Repository: https://github.com/MPOS/php-mpos
- Commit:
236cccd5d3178e99504bf2665db8bddfed6aa176 - Generated: 2026-11-14T14:52:00+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 | 65% | 100% |
| Code quality | 57 | weak | 90% | 100% |
| Security | 60 | 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%
-
Stylometry index: 0.16 per 1,000 lines (narrated steps 11, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2017-01 | 520 | 0% |
| 2017-02 | 1 | 0% |
| 2017-07 | 4 | 0% |
| 2017-08 | 1 | 0% |
| 2017-09 | 68 | 0% |
| 2017-11 | 1 | 0% |
| 2017-12 | 143 | 0% |
| 2018-01 | 2 | 0% |
| 2018-02 | 119 | 0% |
| 2018-03 | 101 | 0% |
| 2018-04 | 53 | 0% |
| 2018-05 | 90 | 0% |
Evidence
- step-by-step narration comment: // Now we can set our additional key prefix (include/clas)
- step-by-step narration comment: * Finally, a light, permissions-checking logging class. (include/lib/)
- step-by-step narration comment: # First, look for nested blocks, e.g.: (include/lib/)
- step-by-step narration comment: # First, handle reference-style links: [link text] [id] (include/lib/)
- step-by-step narration comment: # Next, inline-style links: link text (include/lib/)
- step-by-step narration comment: # First, handle reference-style labeled images: ![alt text][id] (include/lib/)
- step-by-step narration comment: # Next, handle inline images:
(include/lib/)
- step-by-step narration comment: # First, handle reference-style links: [link text] [id] (include/lib/)
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.03, no CI test run detected; 21% of function code in complex or long functions; 13% duplicated lines. Weakest area: process.
| Area | Score |
|---|---|
| Complexity (lizard) | 53 |
| Duplication | 45 |
| Code smells (Opengrep) | 94 |
| Tests and CI | 37 |
| Documentation | 100 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | 35 |
- Functions: 2,594; mean complexity 3.3, 90th percentile 7; 60 complex and 14 long functions
- Duplicated lines: 13.4% of 45,826 compared
- Tests: 2,389 test lines for 70,343 source lines (ratio 0.03); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: none
Most complex functions:
- smarty_function_html_select_time in include/smarty/libs/plugins/function.html_select_time.php: complexity 134, 282 lines
- smarty_function_html_select_date in include/smarty/libs/plugins/function.html_select_date.php: complexity 126, 280 lines
- Smarty_Internal_Utility::testInstall in include/smarty/libs/sysplugins/smarty_internal_utility.php: complexity 91, 483 lines
- Mobile_Detect::mobileGrade in include/lib/Mobile_Detect.php: complexity 75, 52 lines
- (anonymous) in public/site_assets/bootstrap/js/plugins/dataTables/jquery.dataTables.js: complexity 58, 11 lines
Security
Security posture is weak: 84 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 94 |
| Static analysis (Opengrep) | 66 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | 25 |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
- OpenSSF Scorecard aggregate: 3.0/10 (published 2026-11-09)
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
cronjobs/shared.inc.php:29 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/classes/memcache_ad.class.php:15 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/classes/memcache_ad.class.php:64 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/classes/user.class.php:637 |
| high | opengrep/php.lang.security.md5-loose-equality: Make sure comparisons involving md5 values are strict (use === not ==) to avoid type juggling issues [confidence low] |
include/classes/user.class.php:959 |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off: SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] |
include/lib/jsonRPCClient.php:111 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php:85 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php:420 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php:689 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php:68 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php:78 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php:79 |
| 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] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:559 |
| 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] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:560 |
| 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] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:562 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:576 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
include/lib/swiftmailer/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php:583 |
| high | opengrep/php.lang.security.exec-use: Executing non-constant commands. This can lead to command injection. [confidence low] |
include/lib/swiftmailer/classes/Swift/Transport/StreamBuffer.php:292 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/getdashboarddata.inc.php:121 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/gethourlyhashrates.inc.php:17 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/getuserbalance.inc.php:11 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/getuserhashrate.inc.php:21 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/getusersharerate.inc.php:21 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/getuserstatus.inc.php:27 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
include/pages/api/getusertransactions.inc.php:38 |
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: 70,343; test lines: 2,389
| Language | Lines |
|---|---|
| PHP | 70,475 |
| JavaScript | 1,410 |
| Shell | 585 |
| SQL | 262 |