Leaderboard github.com

Qihoo360/poseidon

A search engine which can hold 100 trillion lines of log data.

View repository ↗
Go
★ 1,985
commit 9be3a58756c2
scored 2026-11-14
scoring prov-5+qual-2+sec-2

AI provenance

none-detected

Confidence: 49%
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

75/100

adequate

Confidence: 85%
Coverage: 100%

Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.

Dispute or request a re-score Full report JSON

AI provenance

0% none-detected

No AI attribution or AI-consistent velocity signals detected.

How the score is built

Explicitly attributed share0%
Unattributed share in AI-pace bursts0%
Estimated AI-generated share0%
AI tool configuration files0
Work sessions at AI pace0
Releases at AI pacenot measured
Coding-style index (1.0+ means possible)0.06

Lines added per month all AI-attributed share

2016-100 · 0% AI
2016-1251,592 · 0% AI
2017-0127 · 0% AI
2017-030 · 0% AI
2017-050 · 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: 37
effective_loc: 51,619
tools_detected: 0

AI tool configurationok

artifacts: 0
tools_configured: 0
workflow_agents: 0

Commit velocityok

excluded_import_loc: 45,904
flagged_loc: 0
flagged_loc_share: 0.0%
flagged_units: 0
max_loc_per_hour: 54.25
measured_loc: 270
median_loc_per_hour: 54.25
pr_timed_units: 0
pre_ai_era_burst_loc: 0
pre_ai_era_bursts: 0
pre_ai_era_measured_loc: 270
work_units: 6

Release velocityskipped

Coding styleok2 items

count:assistant_voice: 0
count:emoji_in_code: 0
count:narrated_steps: 2
count:placeholder: 0
files:assistant_voice: 0
files:emoji_in_code: 0
files:narrated_steps: 2
files:placeholder: 0
index: 0.06
lines_scanned: 31,691
per_kloc:assistant_voice: 0
per_kloc:emoji_in_code: 0
per_kloc:narrated_steps: 0.06
per_kloc:placeholder: 0

Code quality

57 weak

Code quality is weak: test-to-source ratio 0.46, no CI test run detected; 21% of function code in complex or long functions; 8% duplicated lines. Weakest area: testing.

How the score is built

Complexity54
Duplication62
Lint and smells68
Tests and CI48
Documentation65
Type safetynot measured
Review processnot measured

Evidence by analyzer

Complexity (lizard)ok10 items

complex_functions: 40
function_nloc: 19,552
functions: 1,399
long_functions: 9
many_param_functions: 0
mean_ccn: 3.70
p90_ccn: 8
risky_nloc_share: 20.5%

Duplication (jscpd)ok10 items

compared_lines: 22,095
duplicated_lines: 1,786
duplicated_share: 8.1%
files: 154

Lintok

category:correctness: 142
findings: 142
scanned_lines: 31,691
weighted_findings: 48.25

Tests and CIok

check:ci_present: no
check:ci_runs_lint: no
check:ci_runs_tests: no
check:has_tests: yes
check:test_ratio: no
check:tests_cochange: no
ci_files: 0
cochange_commits: 8
cochange_share: 12.5%
source_lines: 31,691
test_lines: 14,442
test_ratio: 0.46

Documentationok2 items

README.md README.md
LICENSE LICENSE

check:changelog: no
check:contributing: no
check:license: yes
check:readme: yes
readme_lines: 54

Type safetyskipped

Security

75 adequate

Security posture is adequate: no high-impact findings. Weakest area: posture.

How the score is built

Secrets97
Static analysis (SAST)86
Vulnerable dependenciesnot measured
CI workflowsnot measured
Security posture0
OpenSSF Scorecardnot measured

Evidence by analyzer

OpenSSF Scorecardskipped

no published OpenSSF Scorecard result for this repo

Package registriesskipped

no registry dependencies declared

Secrets (gitleaks)ok

secrets_current: 0
secrets_history: 0
secrets_low_confidence: 0
secrets_nonprod: 1

Static analysis (opengrep)ok

findings: 44
findings_high: 0
findings_low: 0
findings_medium: 44
parse_errors: 0
scanned_lines: 31,691
weighted_findings: 14.15

Dependencies (osv-scanner)skipped

CI workflows (zizmor)skipped

Security postureok

check:dependency_updates: no
check:lockfiles: yes
check:security_policy: no
check:signed_commits: no
signed_commit_share: 0.0%
unpinned_manifests: 0

Release downloadsok

binary_assets: 0
signals: 0
suspicious: 0

Findings

61 medium126 low

Severity	Rule	Location	Message	Tool
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/common/common.go:122	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/common/common.go:68	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/github.com/donnie4w/go-logger/logger/logger.go:101	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/github.com/donnie4w/go-logger/logger/logger.go:84	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	builder/docformat/src/github.com/golang/protobuf/protoc-gen-go/internal/grpc/grpc.go:119	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.use-filepath-join`	builder/docformat/src/github.com/golang/protobuf/protoc-gen-go/internal/grpc/grpc.go:120	`path.Join(...)` always joins using a forward slash. This may cause issues on Windows or other systems using a different delimiter. Use `filepath.Join(...)` instead which uses OS-specific path separators.	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/job/logto_hdfs_collector.go:128	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/job/logto_hdfs_collector.go:497	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/job/logto_hdfs_collector.go:548	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/job/logto_hdfs_collector.go:558	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/job/logto_hdfs_collector.go:697	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	builder/docformat/src/main/main.go:241	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/java.lang.correctness.no-string-eqeq`	builder/index/src/main/java/InvertedIndex/InvertedIndexGenerate.java:75	Strings should not be compared with '=='. This is a reference comparison operator. Use '.equals()' instead.	Lint
medium	`opengrep/java.lang.correctness.no-string-eqeq`	builder/indexmeta/src/main/java/meta/MetaConfigured.java:61	Strings should not be compared with '=='. This is a reference comparison operator. Use '.equals()' instead.	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	service/idgenerator/main.go:36	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	service/proxy/main.go:35	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.correctness.permissions.incorrect-default-permission`	service/searcher/main.go:35	Detected file permissions that are set to more than `0600` (user/owner can read and write). Setting file permissions to higher than `0600` is most likely unnecessary and violates the principle of least privilege. Instead, set...	Lint
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	builder/docformat/src/github.com/bitly/go-nsq/config.go:11	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.unsafe-reflect-by-name`	builder/docformat/src/github.com/bitly/go-nsq/config.go:286	If an attacker can supply values that the application then uses to determine which method or field to invoke, the potential exists for the attacker to create control flow paths through the application that were not intended by the...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.unsafe-reflect-by-name`	builder/docformat/src/github.com/bitly/go-nsq/config.go:361	If an attacker can supply values that the application then uses to determine which method or field to invoke, the potential exists for the attacker to create control flow paths through the application that were not intended by the...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/bitly/go-nsq/config.go:479	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	builder/docformat/src/github.com/bitly/go-nsq/consumer.go:9	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`	builder/docformat/src/github.com/garyburd/redigo/redis/pool.go:317	Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`	builder/docformat/src/github.com/garyburd/redigo/redis/script.go:38	Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:100	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:105	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:110	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:115	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:120	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:125	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:130	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:135	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:140	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:145	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:150	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:185	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:203	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:215	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:239	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:254	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:265	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:57	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:68	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:90	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:95	Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an...	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	builder/docformat/src/job/common.go:10	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`	builder/docformat/src/job/common.go:46	Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	builder/docformat/src/job/logto_hdfs_collector.go:13	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	builder/docformat/src/job/test_collector.go:6	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`	builder/docformat/src/job/test_processor.go:5	Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	Static analysis (opengrep)
medium	`opengrep/java.lang.security.audit.crypto.ssl.defaulthttpclient-is-deprecated`	builder/indexmeta/src/main/java/meta/MetaSetter.java:42	DefaultHttpClient is deprecated. Further, it does not support connections using TLS1.2, which makes using DefaultHttpClient a security hazard. Use HttpClientBuilder instead. [confidence low]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	service/idgenerator/module/idgenerator.go:75	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	service/meta/module/logic.go:132	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	service/meta/module/logic.go:134	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	service/meta/module/logic.go:44	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	service/meta/module/logic.go:47	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-direct-write-to-responsewriter`	service/proxy/module/proxy.go:108	Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'....	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-io-writestring-to-responsewriter`	service/searcher/module/poseidon.go:252	Detected 'io.WriteString()' writing directly to 'http.ResponseWriter'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package to render data to users. [confidence low]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.audit.xss.no-io-writestring-to-responsewriter`	service/searcher/module/poseidon.go:262	Detected 'io.WriteString()' writing directly to 'http.ResponseWriter'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package to render data to users. [confidence low]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.shared-url-struct-mutation`	service/searcher/poseidon/hdfs_reader.go:26	Shared URL struct may have been accidentally mutated. Ensure that this behavior is intended. [confidence low]	Static analysis (opengrep)
medium	`opengrep/go.lang.security.shared-url-struct-mutation`	service/searcher/poseidon/inverted_index_gz_client.go:97	Shared URL struct may have been accidentally mutated. Ensure that this behavior is intended. [confidence low]	Static analysis (opengrep)
low	`opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command`	builder/build.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`	builder/build.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`	builder/build.sh:3	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`	builder/docformat/build.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`	builder/docformat/build.sh:18	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`	builder/docformat/build.sh:19	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`	builder/docformat/build.sh:22	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`	builder/docformat/build.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`	builder/docformat/build.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`	builder/docformat/build.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`	builder/docformat/build.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`	builder/docformat/build.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`	builder/docformat/build.sh:33	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`	builder/docformat/build.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`	builder/docformat/build.sh:37	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`	builder/docformat/build.sh:9	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`	builder/docformat/build.sh:9	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`	builder/docformat/script/common/clean.sh:2	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`	builder/docformat/script/common/clean.sh:2	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`	builder/docformat/script/common/clean.sh:3	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`	builder/docformat/script/common/clean.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`	builder/docformat/script/common/clean.sh:8	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`	builder/docformat/script/common/demo.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`	builder/docformat/script/common/demo.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`	builder/docformat/script/common/demo.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`	builder/docformat/script/common/demo.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-command-substitution-in-command`	builder/docformat/script/common/install.sh:22	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`	builder/docformat/script/common/install.sh:22	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`	builder/docformat/script/common/install.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`	builder/docformat/script/common/install.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`	builder/docformat/script/common/install.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`	builder/docformat/script/common/install.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`	builder/docformat/script/common/install.sh:37	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`	builder/docformat/script/common/install.sh:41	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`	builder/docformat/script/common/install.sh:42	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`	builder/docformat/script/common/local-hadoop.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`	builder/docformat/script/common/local-hadoop.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`	builder/docformat/script/common/local-hadoop.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`	builder/docformat/script/common/local-hadoop.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`	builder/docformat/script/common/real-hadoop.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`	builder/docformat/src/github.com/bitly/go-nsq/test.sh:33	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`	builder/docformat/src/github.com/bitly/go-nsq/test.sh:33	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`	builder/docformat/src/github.com/bitly/go-nsq/test.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`	builder/docformat/src/github.com/bitly/go-nsq/test.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`	builder/index/src/main/bin/demo.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`	builder/index/src/main/bin/demo.sh:18	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`	builder/index/src/main/bin/demo.sh:20	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`	builder/index/src/main/bin/demo.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`	builder/index/src/main/bin/demo.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`	builder/index/src/main/bin/mock_start.sh:20	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`	builder/index/src/main/bin/mock_start.sh:21	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`	builder/index/src/main/bin/mock_start.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`	builder/index/src/main/bin/mock_start.sh:40	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`	builder/index/src/main/bin/mock_start.sh:41	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`	builder/index/src/main/bin/mock_start.sh:42	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`	builder/index/src/main/bin/mock_start.sh:44	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`	builder/index/src/main/bin/mock_start.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`	builder/index/src/main/bin/mock_start.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`	builder/index/src/main/bin/mock_start.sh:51	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`	builder/index/src/main/bin/mock_start.sh:52	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`	builder/index/src/main/bin/mock_start.sh:55	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`	builder/index/src/main/bin/mock_start.sh:57	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`	builder/index/src/main/bin/mock_start.sh:58	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`	builder/index/src/main/bin/mock_start.sh:62	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`	builder/index/src/main/bin/mock_start.sh:63	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`	builder/index/src/main/bin/mock_start.sh:64	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`	builder/index/src/main/bin/mock_start.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`	builder/index/src/main/bin/mock_start.sh:73	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`	builder/index/src/main/bin/mock_start.sh:74	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`	builder/index/src/main/bin/mock_start.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-variable-expansion-in-command`	builder/index/src/main/bin/mock_start.sh:85	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`	builder/index/src/main/bin/mock_start.sh:86	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`	builder/index/src/main/bin/start.sh:15	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`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.sh:18	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`	builder/index/src/main/bin/start.sh:39	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`	builder/index/src/main/bin/start.sh:40	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`	builder/index/src/main/bin/start.sh:41	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`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.sh:46	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`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.sh:52	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`	builder/index/src/main/bin/start.sh:54	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`	builder/index/src/main/bin/start.sh:56	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`	builder/index/src/main/bin/start.sh:58	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`	builder/index/src/main/bin/start.sh:59	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`	builder/index/src/main/bin/start.sh:61	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`	builder/index/src/main/bin/start.sh:62	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`	builder/index/src/main/bin/start.sh:65	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`	builder/index/src/main/bin/start.sh:66	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`	builder/index/src/main/bin/start.sh:73	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`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.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-variable-expansion-in-command`	builder/index/src/main/bin/start.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-variable-expansion-in-command`	builder/index/src/main/bin/start.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-variable-expansion-in-command`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.sh:9	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`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.sh:92	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`	builder/index/src/main/bin/start.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`	builder/index/src/main/bin/start.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`	common/proto/build.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`	common/proto/build.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`	service/allinone/build.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`	service/allinone/build.sh:21	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`	service/hdfsreader/src/main/script/hdfsReader.sh:3	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`	service/hdfsreader/src/main/script/hdfsReader.sh:3	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`	service/hdfsreader/src/main/script/hdfsReader.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`	service/hdfsreader/src/main/script/hdfsReader.sh:39	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`	service/hdfsreader/src/main/script/hdfsReader.sh:4	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`	service/hdfsreader/src/main/script/hdfsReader.sh:43	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`	service/hdfsreader/src/main/script/hdfsReader.sh:44	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`	service/hdfsreader/src/main/script/hdfsReader.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`	service/hdfsreader/src/main/script/hdfsReader.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`	service/idgenerator/build.sh:15	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`	service/idgenerator/build.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`	service/idgenerator/build.sh:8	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`	service/meta/build.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`	service/meta/build.sh:21	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`	service/proxy/build.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`	service/proxy/build.sh:21	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`	service/searcher/build.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`	service/searcher/build.sh:21	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`	test.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`	test.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	`gitleaks/private-key`	builder/docformat/src/github.com/bitly/go-nsq/test/server.key:1	Possible private-key secret in the current tree (test/docs/example file)	Secrets (gitleaks)

Tools and coverage

Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.

Analyzer	Pillar	Status	Version	Findings	Note
AI tool configuration	AI provenance	ok	`signatures-v1`	0
Explicit AI attribution	AI provenance	ok	`signatures-v1`	0
Release velocity	AI provenance	skipped	`—`	0
Coding style	AI provenance	ok	`—`	0
Commit velocity	AI provenance	ok	`prov-4`	0
Complexity (lizard)	Code quality	ok	`lizard 1.25.1`	0
Documentation	Code quality	ok	`—`	0
Duplication (jscpd)	Code quality	ok	`repotrust-dup-w6`	0
Lint	Code quality	ok	`opengrep 1.33.1; rules f1d2b562b414`	142
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`	44
OpenSSF Scorecard	Security	skipped	`—`	0	no published OpenSSF Scorecard result for this repo
Secrets (gitleaks)	Security	ok	`gitleaks 8.30.1`	1

Score history

Scores from different scoring versions aren't directly comparable.

Scored	Commit	Scoring	AI provenance	Quality	Security
2026-11-14	`9be3a58756c2`	`prov-5+qual-2+sec-2`	0%	57	75
2026-11-14	`9be3a58756c2`	`prov-4+qual-2+sec-2`	0%	57	75

Embed a badge

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

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/Qihoo360/poseidon/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Qihoo360/poseidon/)

[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Qihoo360/poseidon/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Qihoo360/poseidon/)

[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Qihoo360/poseidon/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Qihoo360/poseidon/)

Full text report

Repository: https://github.com/Qihoo360/poseidon
Commit: 9be3a58756c2c604573075b6e7531f13f5ba7c1c
Generated: 2026-11-14T14:52:01+00:00
Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2

Scores

Pillar	Score	Signal	Confidence	Coverage
AI provenance (estimated AI-generated share)	0	none-detected	49%	100%
Code quality	57	weak	90%	100%
Security	75	adequate	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.06 per 1,000 lines (narrated steps 2, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.

Month	Lines added	Attributed to AI
2016-12	51,592	0%
2017-01	27	0%

Evidence

step-by-step narration comment: // First, find the last element (builder/docf)
step-by-step narration comment: // step 3. filter docId list (service/sear)

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.46, no CI test run detected; 21% of function code in complex or long functions; 8% duplicated lines. Weakest area: testing.

Area	Score
Complexity (lizard)	54
Duplication	62
Code smells (Opengrep)	68
Tests and CI	48
Documentation	65
Type safety	n/a
Process (Scorecard review/maintenance)	n/a

Functions: 1,399; mean complexity 3.7, 90th percentile 8; 40 complex and 9 long functions
Duplicated lines: 8.1% of 22,095 compared
Tests: 14,442 test lines for 31,691 source lines (ratio 0.46); CI test commands: none detected; 12% of recent source commits also change tests
Docs missing or thin: contributing, changelog

Most complex functions:

Security

Security posture is adequate: no high-impact findings. Weakest area: posture.

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

Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits

Top findings

Severity	Finding	Location
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`: Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	builder/docformat/src/github.com/bitly/go-nsq/config.go:11
medium	`opengrep/go.lang.security.audit.unsafe-reflect-by-name`: If an attacker can supply values that the application then uses to determine which method or field to invoke, the potential exists for the attacker to create control flow paths through the application that were not intended by the application developers. This attack vector may allow the attacker to [confidence low]	builder/docformat/src/github.com/bitly/go-nsq/config.go:286
medium	`opengrep/go.lang.security.audit.unsafe-reflect-by-name`: If an attacker can supply values that the application then uses to determine which method or field to invoke, the potential exists for the attacker to create control flow paths through the application that were not intended by the application developers. This attack vector may allow the attacker to [confidence low]	builder/docformat/src/github.com/bitly/go-nsq/config.go:361
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/bitly/go-nsq/config.go:479
medium	`opengrep/go.lang.security.audit.crypto.math-random-used`: Do not use `math/rand`. Use `crypto/rand` instead. [confidence medium]	builder/docformat/src/github.com/bitly/go-nsq/consumer.go:9
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`: Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	builder/docformat/src/github.com/garyburd/redigo/redis/pool.go:317
medium	`opengrep/go.lang.security.audit.crypto.use-of-sha1`: Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. [confidence medium]	builder/docformat/src/github.com/garyburd/redigo/redis/script.go:38
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:57
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:68
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:90
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:95
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:100
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:105
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:110
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:115
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:120
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:125
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:130
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:135
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:140
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:145
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:150
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:185
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:203
medium	`opengrep/go.lang.security.audit.use-of-unsafe-block`: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low]	builder/docformat/src/github.com/golang/protobuf/proto/pointer_unsafe.go:215

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: 31,691; test lines: 14,442

Language	Lines
Go	38,910
Java	6,510
Shell	713