Leaderboard github.com
CMU-Perceptual-Computing-Lab/openpose
OpenPose: Real-time multi-person keypoint detection library for body, face, hands, and foot estimation
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
54/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
64/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.19
Lines added per month all AI-attributed share
- 2017-04109,822 · 0% AI
- 2017-05869 · 0% AI
- 2017-067,167 · 0% AI
- 2017-074,689 · 0% AI
- 2017-08192 · 0% AI
- 2017-09943 · 0% AI
- 2017-105,860 · 0% AI
- 2017-11900 · 0% AI
- 2017-121,349 · 0% AI
- 2018-013,840 · 0% AI
- 2018-0213,910 · 0% AI
- 2018-031,300 · 0% AI
- 2018-041,762 · 0% AI
- 2018-055,297 · 0% AI
- 2018-067,257 · 0% AI
- 2018-07665 · 0% AI
- 2018-08141 · 0% AI
- 2018-095,679 · 0% AI
- 2018-101,683 · 0% AI
- 2018-112,586 · 0% AI
- 2018-122,775 · 0% AI
- 2019-016,617 · 0% AI
- 2019-022,642 · 0% AI
- 2019-03447 · 0% AI
- 2019-04899 · 0% AI
- 2019-051,576 · 0% AI
- 2019-07197 · 0% AI
- 2019-08103 · 0% AI
- 2019-0999 · 0% AI
- 2019-105,041 · 0% AI
- 2019-11170 · 0% AI
- 2019-120 · 0% AI
- 2020-010 · 0% AI
- 2020-04434 · 0% AI
- 2020-06130 · 0% AI
- 2020-070 · 0% AI
- 2020-0913 · 0% AI
- 2020-10153 · 0% AI
- 2020-1167 · 0% AI
- 2020-121 · 0% AI
- 2021-01402 · 0% AI
- 2021-020 · 0% AI
- 2021-041 · 0% AI
- 2021-091 · 0% AI
- 2021-114 · 0% AI
- 2021-121 · 0% AI
- 2022-010 · 0% AI
- 2022-0374 · 0% AI
- 2022-051 · 0% AI
- 2022-062 · 0% AI
- 2022-090 · 0% AI
- 2022-100 · 0% AI
- 2023-040 · 0% AI
- 2023-060 · 0% AI
- 2023-070 · 0% AI
- 2023-120 · 0% AI
- 2024-010 · 0% AI
- 2024-030 · 0% AI
- 2024-041 · 0% AI
- 2024-081 · 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
- 704
- effective_loc
- 197,763
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 107,808
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 2,607.96
- measured_loc
- 89,955
- median_loc_per_hour
- 69
- pr_timed_units
- 88
- pre_ai_era_burst_loc
- 28,287
- pre_ai_era_bursts
- 7
- pre_ai_era_measured_loc
- 89,870
- work_units
- 416
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 245.20
- releases
- 14
Coding styleok8 items
- step-by-step narration comment: // Step 1 - Set logging level
- step-by-step narration comment: // Step 2 - Read GFlags (user defined configuration)
- step-by-step narration comment: // Step 3 - Setting producer
- step-by-step narration comment: // Step 4 - Setting thread workers && manager
- step-by-step narration comment: // Step 5 - Initializing the worker classes
- step-by-step narration comment: // then, we can group the last 2 in the same thread and keep wGui in a different thread:
- step-by-step narration comment: // Step 1 - Set logging level
- step-by-step narration comment: // Step 2 - Setting thread workers && manager
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 12
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 5
- files:placeholder
- 0
- index
- 0.19
- lines_scanned
- 64,254
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.19
- per_kloc:placeholder
- 0
Code quality
54 weak
Code quality is weak: test-to-source ratio 0.02, no CI test run detected; 15% of function code in complex or long functions; 20% duplicated lines. Weakest area: duplication.
How the score is built
- Complexity64
- Duplication30
- Lint and smells94
- Tests and CI42
- Documentation65
- Type safety40
- Review process40
Evidence by analyzer
Complexity (lizard)ok10 items
- op::configureThreadManager in include/openpose/wrapper/wrapperAuxiliary.hpp: complexity 193, 874 lines
- op::wrapperConfigureSanityChecks in src/openpose/wrapper/wrapperAuxiliary.cpp: complexity 67, 172 lines
- op::OpenCL::clErrorToString in src/openpose/gpu/opencl.cpp: complexity 63, 74 lines
- op::handleWaitKey in src/openpose/gui/gui.cpp: complexity 60, 136 lines
- op::createPeopleVector in src/openpose/net/bodyPartConnectorBase.cpp: complexity 58, 252 lines
- op::CocoJsonSaver::record in src/openpose/filestream/cocoJsonSaver.cpp: complexity 41, 150 lines
- op::pafVectorIntoPeopleVector in src/openpose/net/bodyPartConnectorBase.cpp: complexity 41, 110 lines
- op::PoseExtractorCaffe::forwardPass in src/openpose/pose/poseExtractorCaffe.cpp: complexity 41, 255 lines
- op::nmsRegisterKernelCPU in src/openpose/net/nmsBase.cpp: complexity 39, 53 lines
- op::PoseExtractorNet::getHeatMapsCopy in src/openpose/pose/poseExtractorNet.cpp: complexity 36, 106 lines
- complex_functions
- 40
- function_nloc
- 34,235
- functions
- 2,010
- long_functions
- 19
- many_param_functions
- 57
- mean_ccn
- 3.42
- p90_ccn
- 7
- risky_nloc_share
- 15.0%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: examples/calibration/calibration.cpp:125 and examples/deprecated/tutorial_add_module_custom_post_processing.cpp:172
- 6+ duplicated lines: examples/calibration/calibration.cpp:127 and examples/openpose/openpose.cpp:147
- 6+ duplicated lines: examples/deprecated/tutorial_add_module/wUserPostProcessing.hpp:65 and include/openpose/3d/wJointAngleEstimation.hpp:82
- 6+ duplicated lines: examples/deprecated/tutorial_add_module_custom_post_processing.cpp:37 and examples/openpose/openpose.cpp:20
- 6+ duplicated lines: examples/deprecated/tutorial_add_module_custom_post_processing.cpp:47 and examples/deprecated/tutorial_api_thread_1_user_processing_function.cpp:73
- 6+ duplicated lines: examples/deprecated/tutorial_add_module_custom_post_processing.cpp:90 and examples/tutorial_api_cpp/13_asynchronous_custom_input_output_and_datum.cpp:231
- 6+ duplicated lines: examples/deprecated/tutorial_api_thread_1_user_processing_function.cpp:2 and examples/deprecated/tutorial_api_thread_2_user_input_processing_output_and_datum.cpp:2
- 6+ duplicated lines: examples/deprecated/tutorial_api_thread_2_user_input_processing_output_and_datum.cpp:19 and include/openpose/flags.hpp:15
- 6+ duplicated lines: examples/deprecated/tutorial_api_thread_2_user_input_processing_output_and_datum.cpp:31 and examples/tutorial_api_cpp/13_asynchronous_custom_input_output_and_datum.cpp:23
- 6+ duplicated lines: examples/deprecated/tutorial_api_thread_2_user_input_processing_output_and_datum.cpp:48 and examples/tutorial_api_cpp/18_synchronous_custom_all_and_datum.cpp:38
- compared_lines
- 42,025
- duplicated_lines
- 8,438
- duplicated_share
- 20.1%
- files
- 380
Lintok
- category:correctness
- 64
- findings
- 64
- scanned_lines
- 64,254
- weighted_findings
- 16
Tests and CIok1 item
- CI config: .github/workflows/main.yml
.github/workflows/main.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
- 187
- cochange_share
- 16.0%
- source_lines
- 64,254
- test_lines
- 1,148
- test_ratio
- 0.02
Documentationok2 items
- README.md
README.md - LICENSE
LICENSE
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 138
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 0
- escapes_per_kloc
- 0
Security
64 weak
Security posture is weak: 3 high-severity workflow issues. Weakest area: posture.
How the score is built
- Secrets85
- Static analysis (SAST)100
- Vulnerable dependenciesnot measured
- CI workflows52
- Security posture0
- OpenSSF Scorecard21
Evidence by analyzer
OpenSSF Scorecardok13 items
- Scorecard Code-Review: 8/10 (Found 24/30 approved changesets -- score normalized to 8)
- Scorecard Dangerous-Workflow: 10/10 (no dangerous workflow patterns detected)
- Scorecard Maintained: 0/10 (0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0)
- Scorecard Token-Permissions: 0/10 (detected GitHub workflow tokens with excessive permissions)
- Scorecard Binary-Artifacts: 7/10 (binaries present in source code)
- 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 Pinned-Dependencies: 0/10 (dependency not pinned by hash detected -- score normalized to 0)
- Scorecard License: 9/10 (license file detected)
- Scorecard Fuzzing: 0/10 (project is not fuzzed)
- Scorecard Signed-Releases: 0/10 (Project has not signed or included provenance with any releases.)
- 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
- 2.90
- check:Binary-Artifacts
- yes
- check:Branch-Protection
- no
- check:CII-Best-Practices
- no
- check:Code-Review
- yes
- check:Dangerous-Workflow
- yes
- check:Fuzzing
- no
- check:License
- yes
- check:Maintained
- no
- check:Pinned-Dependencies
- no
- check:SAST
- no
- check:Security-Policy
- no
- check:Signed-Releases
- no
- check:Token-Permissions
- no
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 5
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 1
- findings_high
- 0
- findings_low
- 0
- findings_medium
- 1
- parse_errors
- 1
- scanned_lines
- 64,254
- weighted_findings
- 0.25
Dependencies (osv-scanner)skipped
CI workflows (zizmor)ok
- findings
- 5
- findings_high
- 3
- findings_low
- 0
- findings_medium
- 2
- penalty
- 39.60
- workflows
- 1
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 30.0%
- unpinned_manifests
- 0
Release downloadsok5 items
- release v1.7.0 ships openpose-1.7.0-binaries-win64-cpu-python3.7-flir-3d.zip (62821 downloads)
- release v1.7.0 ships openpose-1.7.0-binaries-win64-gpu-python3.7-flir-3d_recommended.zip (109080 downloads)
- release v1.6.0 ships openpose-1.6.0-binaries-win64-gpu-flir-3d_recommended.zip (24131 downloads)
- release v1.6.0 ships openpose-1.6.0-binaries-win64-only_cpu-flir-3d.zip (11643 downloads)
- release v1.5.1 ships openpose-1.5.1-binaries-win64-gpu-flir-3d_recommended.zip (19140 downloads)
- binary_assets
- 19
- signals
- 1
- suspicious
- 0
Findings
3 high3 medium69 low
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | zizmor/unpinned-uses |
.github/workflows/main.yml:233 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/main.yml:237 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/main.yml:283 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/main.yml:12 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/artipacked |
.github/workflows/main.yml:233 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| medium | opengrep/bash.curl.security.curl-pipe-bash |
scripts/osx/install_brew.sh:3 | Data is being piped into `bash` from a `curl` command. An attacker with control of the server in the `curl` command could inject malicious code into the pipe, resulting in a system compromise. Avoid piping untrusted data into `bash` or... | Static analysis (opengrep) |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
.github/CI_deprecated/generate_gh_pages.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 |
.github/CI_deprecated/generate_gh_pages.sh:48 | 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 |
.github/CI_deprecated/generate_gh_pages.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 |
models/getModels.sh:12 | 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 |
models/getModels.sh:17 | 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 |
models/getModels.sh:26 | 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 |
models/getModels.sh:31 | 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 |
models/getModels.sh:36 | 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 |
scripts/CI/configure.sh:11 | 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 |
scripts/CI/configure.sh:14 | 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 |
scripts/CI/configure.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 |
scripts/CI/configure.sh:6 | 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 |
scripts/CI/configure_cmake.sh:71 | 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 |
scripts/CI/configure_cmake.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 |
scripts/CI/install_deps_osx.sh:6 | 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 |
scripts/CI/install_deps_osx.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 |
scripts/CI/install_deps_ubuntu.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-variable-expansion-in-command |
scripts/CI/install_deps_ubuntu.sh:13 | 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 |
scripts/CI/install_deps_ubuntu.sh:16 | 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 |
scripts/CI/install_deps_ubuntu.sh:6 | 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 |
scripts/CI/install_deps_ubuntu.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-command-substitution-in-command |
scripts/CI/run_make.sh:10 | 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 |
scripts/CI/run_make.sh:11 | 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 |
scripts/CI/run_make.sh:13 | 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 |
scripts/CI/run_make.sh:14 | 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 |
scripts/CI/run_make.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 |
scripts/CI/run_make.sh:6 | 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 |
scripts/CI/run_tests.sh:103 | 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 |
scripts/CI/run_tests.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 |
scripts/CI/run_tests.sh:6 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.1.sh:26 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.1.sh:28 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.1.sh:30 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.1.sh:32 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.3.sh:26 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.3.sh:28 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.3.sh:30 | 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 |
scripts/ubuntu/install_caffe_and_openpose_JetsonTX2_JetPack3.3.sh:32 | 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 |
scripts/ubuntu/install_cuda.sh:16 | 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 |
scripts/ubuntu/install_cuda.sh:23 | 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 |
scripts/ubuntu/install_cuda.sh:32 | 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 |
scripts/ubuntu/install_cuda.sh:35 | 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 |
scripts/ubuntu/install_cuda.sh:45 | 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 |
scripts/ubuntu/install_cuda.sh:48 | 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 |
scripts/ubuntu/install_cudnn_up_to_Ubuntu16.sh:14 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.1.sh:24 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.1.sh:26 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.1.sh:28 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.1.sh:30 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.1.sh:48 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.3.sh:24 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.3.sh:26 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.3.sh:28 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.3.sh:30 | 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 |
scripts/ubuntu/install_openpose_JetsonTX2_JetPack3.3.sh:41 | 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 |
scripts/ubuntu_deprecated/install_caffe_and_openpose_if_cuda8.sh:26 | 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 |
scripts/ubuntu_deprecated/install_caffe_and_openpose_if_cuda8.sh:28 | 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 |
scripts/ubuntu_deprecated/install_caffe_and_openpose_if_cuda8.sh:30 | 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 |
scripts/ubuntu_deprecated/install_caffe_and_openpose_if_cuda8.sh:32 | 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 |
scripts/ubuntu_deprecated/install_openpose_if_cuda8.sh:25 | 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 |
scripts/ubuntu_deprecated/install_openpose_if_cuda8.sh:27 | 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 |
scripts/ubuntu_deprecated/install_openpose_if_cuda8.sh:29 | 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 |
scripts/ubuntu_deprecated/install_openpose_if_cuda8.sh:31 | 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 |
scripts/ubuntu_deprecated/install_openpose_if_cuda8.sh:42 | 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 | gitleaks/generic-api-key |
include/openpose/3d/wJointAngleEstimation.hpp:68 | Possible generic-api-key secret in history (commit 0c1f14f79c); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
include/openpose/3d/wPoseTriangulation.hpp:77 | Possible generic-api-key secret in history (commit 6477264f8c); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
include/openpose/filestream/wPeopleJsonSaver.hpp:83 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
src/openpose/gui/gui.cpp:177 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
src/openpose/gui/gui3D.cpp:499 | Possible generic-api-key secret in the current tree | 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-5 | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-5 | 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 | 64 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | ok | zizmor 1.32.0 | 5 | |
| 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 | 1 | |
| OpenSSF Scorecard | Security | ok | scorecard v5.6.0 | 0 | |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 5 |
Score history
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 5c5d96523ef9 | prov-5+qual-2+sec-2 | 0% | 54 | 64 |
Full text report
- Repository: https://github.com/CMU-Perceptual-Computing-Lab/openpose
- Commit:
5c5d96523ef917bd30301245fdc8343937cae48d - Generated: 2026-11-14T15:16:14+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 | 54 | weak | 90% | 100% |
| Security | 64 | 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.19 per 1,000 lines (narrated steps 12, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2020-11 | 67 | 0% |
| 2020-12 | 1 | 0% |
| 2021-01 | 402 | 0% |
| 2021-04 | 1 | 0% |
| 2021-09 | 1 | 0% |
| 2021-11 | 4 | 0% |
| 2021-12 | 1 | 0% |
| 2022-03 | 74 | 0% |
| 2022-05 | 1 | 0% |
| 2022-06 | 2 | 0% |
| 2024-04 | 1 | 0% |
| 2024-08 | 1 | 0% |
Evidence
- step-by-step narration comment: // Step 1 - Set logging level (examples/dep)
- step-by-step narration comment: // Step 2 - Read GFlags (user defined configuration) (examples/dep)
- step-by-step narration comment: // Step 3 - Setting producer (examples/dep)
- step-by-step narration comment: // Step 4 - Setting thread workers && manager (examples/dep)
- step-by-step narration comment: // Step 5 - Initializing the worker classes (examples/dep)
- step-by-step narration comment: // then, we can group the last 2 in the same thread and keep wGui in a different thread: (examples/dep)
- step-by-step narration comment: // Step 1 - Set logging level (examples/dep)
- step-by-step narration comment: // Step 2 - Setting thread workers && manager (examples/dep)
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.02, no CI test run detected; 15% of function code in complex or long functions; 20% duplicated lines. Weakest area: duplication.
| Area | Score |
|---|---|
| Complexity (lizard) | 64 |
| Duplication | 30 |
| Code smells (Opengrep) | 94 |
| Tests and CI | 42 |
| Documentation | 65 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | 40 |
- Functions: 2,010; mean complexity 3.4, 90th percentile 7; 40 complex and 19 long functions
- Duplicated lines: 20.1% of 42,025 compared
- Tests: 1,148 test lines for 64,254 source lines (ratio 0.02); CI test commands: none detected; 16% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- op::configureThreadManager in include/openpose/wrapper/wrapperAuxiliary.hpp: complexity 193, 874 lines
- op::wrapperConfigureSanityChecks in src/openpose/wrapper/wrapperAuxiliary.cpp: complexity 67, 172 lines
- op::OpenCL::clErrorToString in src/openpose/gpu/opencl.cpp: complexity 63, 74 lines
- op::handleWaitKey in src/openpose/gui/gui.cpp: complexity 60, 136 lines
- op::createPeopleVector in src/openpose/net/bodyPartConnectorBase.cpp: complexity 58, 252 lines
Security
Security posture is weak: 3 high-severity workflow issues. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 85 |
| Static analysis (Opengrep) | 100 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | 52 |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | 21 |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
- OpenSSF Scorecard aggregate: 2.9/10 (published 2026-11-09)
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/main.yml:233 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/main.yml:237 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/main.yml:283 |
| medium | opengrep/bash.curl.security.curl-pipe-bash: Data is being piped into bash from a curl command. An attacker with control of the server in the curl command could inject malicious code into the pipe, resulting in a system compromise. Avoid piping untrusted data into bash or any other shell if you can. If you must do this, consider checki [confidence low] |
scripts/osx/install_brew.sh:3 |
| medium | zizmor/artipacked: credential persistence through GitHub Actions artifacts [confidence low] |
.github/workflows/main.yml:233 |
| medium | zizmor/excessive-permissions: overly broad permissions [confidence medium] |
.github/workflows/main.yml:12 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
include/openpose/filestream/wPeopleJsonSaver.hpp:83 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
src/openpose/gui/gui.cpp:177 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
src/openpose/gui/gui3D.cpp:499 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 0c1f14f79c); removed from the current tree but still retrievable |
include/openpose/3d/wJointAngleEstimation.hpp:68 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 6477264f8c); removed from the current tree but still retrievable |
include/openpose/3d/wPoseTriangulation.hpp:77 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Distribution signals
- binary-release-asset: release v1.7.0 ships openpose-1.7.0-binaries-win64-cpu-python3.7-flir-3d.zip (62821 downloads)
- binary-release-asset: release v1.7.0 ships openpose-1.7.0-binaries-win64-gpu-python3.7-flir-3d_recommended.zip (109080 downloads)
- binary-release-asset: release v1.6.0 ships openpose-1.6.0-binaries-win64-gpu-flir-3d_recommended.zip (24131 downloads)
- binary-release-asset: release v1.6.0 ships openpose-1.6.0-binaries-win64-only_cpu-flir-3d.zip (11643 downloads)
- binary-release-asset: release v1.5.1 ships openpose-1.5.1-binaries-win64-gpu-flir-3d_recommended.zip (19140 downloads)
Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.
Repository profile
- Source lines: 64,254; test lines: 1,148
| Language | Lines |
|---|---|
| C++ | 63,168 |
| Shell | 1,311 |
| Python | 847 |
| HCL | 76 |