Leaderboard github.com
ferventdesert/Hawk
visualized crawler & ETL IDE written with C#/WPF
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
47/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
68/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% 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.00
Lines added per month all AI-attributed share
- 2016-0423,719 · 0% AI
- 2016-052,602 · 0% AI
- 2016-06212 · 0% AI
- 2016-07164 · 0% AI
- 2016-09240 · 0% AI
- 2016-103,883 · 0% AI
- 2016-11967 · 0% AI
- 2017-0372 · 0% AI
- 2017-050 · 0% AI
- 2017-094 · 0% AI
- 2017-1019 · 0% AI
- 2017-110 · 0% AI
- 2017-121,577 · 0% AI
- 2018-014,033 · 0% AI
- 2018-02795 · 0% AI
- 2018-03276 · 0% AI
- 2018-041,277 · 0% AI
- 2018-051,401 · 0% AI
- 2018-071,306 · 0% AI
- 2018-081,612 · 0% AI
- 2018-091,503 · 0% AI
- 2018-103,619 · 0% AI
- 2018-111,413 · 0% AI
- 2018-1292 · 0% AI
- 2019-012,212 · 0% AI
- 2019-0326 · 0% AI
- 2019-040 · 0% AI
- 2019-056 · 0% AI
- 2019-0686 · 0% AI
- 2019-07266 · 0% AI
- 2019-0865 · 0% AI
- 2019-1256 · 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
- 238
- effective_loc
- 53,503
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 22,567
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 696
- measured_loc
- 30,936
- median_loc_per_hour
- 72.46
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 2,784
- pre_ai_era_bursts
- 1
- pre_ai_era_measured_loc
- 30,936
- work_units
- 139
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 50
- releases
- 6
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0
- lines_scanned
- 36,155
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
47 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 13% of function code in complex or long functions; 15% duplicated lines. Weakest area: testing.
How the score is built
- Complexity67
- Duplication40
- Lint and smells96
- Tests and CI0
- Documentation65
- Type safety40
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- SmartETLTool::RefreshSamples in Hawk.ETL/Process/SmartETLTool.cs: complexity 46, 195 lines
- DataProcessManager::Init in Hawk.ETL/Managements/DataProcessManager.cs: complexity 37, 470 lines
- DataManager::Init in Hawk.ETL/Managements/DataManager.cs: complexity 33, 350 lines
- XPathAnalyzer::GetDiff in Hawk.ETL/Crawlers/XPathAnalyzer.cs: complexity 22, 40 lines
- XPathAnalyzer::GetDiff in Hawk.ETL/Crawlers/XPathx.cs: complexity 22, 40 lines
- ETLHelper::FuncAdd in Hawk.ETL/Interfaces/IColumnDataSorter.cs: complexity 22, 111 lines
- SmartETLTool::ExecuteDatas in Hawk.ETL/Process/SmartETLTool.cs: complexity 22, 119 lines
- XPathAnalyzer::GetDiffNodes in Hawk.ETL/Crawlers/XPathAnalyzer.cs: complexity 21, 110 lines
- XPathAnalyzer::GetDiffNodes in Hawk.ETL/Crawlers/XPathx.cs: complexity 21, 110 lines
- SmartCrawler::GetXPathAsync in Hawk.ETL/Process/SmartCrawler.cs: complexity 20, 100 lines
- complex_functions
- 16
- function_nloc
- 20,213
- functions
- 1,399
- long_functions
- 13
- many_param_functions
- 1
- mean_ccn
- 2.82
- p90_ccn
- 6
- risky_nloc_share
- 13.4%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: Hawk.Core/Connectors/DBConnectorBase.cs:409 and Hawk.Core/Connectors/DataCollection.cs:77
- 6+ duplicated lines: Hawk.Core/Connectors/FileConnectorXML.cs:73 and Hawk.Core/Connectors/FileConnectorXML.cs:103
- 6+ duplicated lines: Hawk.Core/Connectors/MongoDBConnector.cs:530 and Hawk.Core/Connectors/MongoDBConnector.cs:554
- 6+ duplicated lines: Hawk.Core/Connectors/Vitural/AsyncVirtualizingCollection.cs:23 and Hawk.Core/Connectors/Vitural/AsyncVirtualizingCollection.cs:34
- 6+ duplicated lines: Hawk.Core/Connectors/Vitural/DataBaseVirtualCollection.cs:25 and Hawk.Core/Connectors/Vitural/DataBaseVirtualProvider.cs:25
- 6+ duplicated lines: Hawk.Core/Connectors/Vitural/EnumableVirtualCollection.cs:17 and Hawk.Core/Connectors/Vitural/EnumableVirtualProvider.cs:17
- 6+ duplicated lines: Hawk.Core/Connectors/Vitural/VirtualizingCollection.cs:311 and Hawk.Core/Connectors/Vitural/VirtualizingCollection.cs:335
- 6+ duplicated lines: Hawk.Core/Properties/AssemblyInfo.cs:13 and Hawk.ETL.Controls/Properties/AssemblyInfo.cs:15
- 6+ duplicated lines: Hawk.Core/Properties/AssemblyInfo.cs:15 and Hawk.ETL/Properties/AssemblyInfo.cs:15
- 6+ duplicated lines: Hawk.Core/Utils/ControlsExtended.cs:136 and Hawk.Core/Utils/ControlsExtended.cs:181
- compared_lines
- 20,090
- duplicated_lines
- 3,032
- duplicated_share
- 15.1%
- files
- 212
Lintok
- category:best-practice
- 15
- findings
- 15
- scanned_lines
- 36,155
- weighted_findings
- 5.25
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 0
- cochange_commits
- 151
- cochange_share
- 0.0%
- source_lines
- 36,155
- test_lines
- 0
- test_ratio
- 0
Documentationok2 items
- README.md
README.md - LICENSE
LICENSE
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 37
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 0
- escapes_per_kloc
- 0
Security
68 weak
Security posture is weak: 5 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets79
- Static analysis (SAST)89
- 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
- 7
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 8
- findings_high
- 5
- findings_low
- 0
- findings_medium
- 3
- parse_errors
- 0
- scanned_lines
- 36,155
- weighted_findings
- 12
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.5%
- unpinned_manifests
- 0
Release downloadsok5 items
- release v5.2 ships Hawk5.2.zip (6526 downloads)
- release Hawk5.1 ships Hawk5.1.zip (1704 downloads)
- release v5.0 ships Hawk5.1.zip (59 downloads)
- release v5.0 ships Hawk5.zip (2391 downloads)
- release Hawk3 ships Hawk3_Release.zip (3005 downloads)
- binary_assets
- 5
- signals
- 1
- suspicious
- 0
Findings
5 high5 medium20 low
30 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Hawk.Core/Connectors/MySQLConnector.cs:46 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Hawk.Core/Connectors/SQLServerConnector.cs:43 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Hawk.Core/Connectors/SQLiteConnector.cs:209 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Hawk.Core/Connectors/SQLiteConnector.cs:383 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Hawk.Core/Connectors/SQLiteConnector.cs:39 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| medium | opengrep/python.requests.best-practice.use-raise-for-status |
Docs/trans_img.py:16 | There's an HTTP request made with requests, but the raise_for_status() utility method isn't used. This can result in request errors going unnoticed and your code behaving in unexpected ways, such as if your authorization API returns a... | Lint |
| medium | opengrep/python.requests.best-practice.use-timeout |
Docs/trans_img.py:16 | Detected a 'requests' call without a timeout set. By default, 'requests' calls wait until the connection is closed. This means a 'requests' call without a timeout will hang the program if a response is never received. Consider setting a... | Lint |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-binaryformatter-deserialization |
Hawk.Core/Utils/CustomSerializer.cs:31 | The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is... | Static analysis (opengrep) |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-binaryformatter-deserialization |
Hawk.Core/Utils/CustomSerializer.cs:46 | The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is... | Static analysis (opengrep) |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-binaryformatter-deserialization |
Hawk.Core/Utils/CustomSerializer.cs:61 | The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is... | Static analysis (opengrep) |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.Core/Connectors/DBConnectorBase.cs:514 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.Core/Connectors/MySQLConnector.cs:53 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.Core/Connectors/MySQLConnector.cs:68 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.Core/Connectors/SQLiteConnector.cs:214 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.Core/Connectors/SQLiteConnector.cs:245 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.ETL/Crawlers/HttpHelper.cs:584 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.ETL/Crawlers/HttpHelper.cs:588 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.ETL/Crawlers/XPathAnalyzer.cs:1059 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
Hawk.ETL/Crawlers/XPathx.cs:1058 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
HawkScheduler/Program.cs:147 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
HawkScheduler/Program.cs:152 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
HawkScheduler/Program.cs:161 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
HawkScheduler/Program.cs:98 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | gitleaks/generic-api-key |
Hawk.Base/Plugins/Web/BaiduLocation.cs:12 | Possible generic-api-key secret in history (commit 8954d2cad1); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
Hawk.Base/Plugins/Web/NlpTF.cs:24 | Possible generic-api-key secret in history (commit 8954d2cad1); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
Hawk.ETL/Plugins/Web/BaiduLocation.cs:17 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
Hawk.ETL/Plugins/Web/NlpTF.cs:28 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
Hawk/Lang/DefaultLanguage.xaml:1193 | Possible generic-api-key secret in history (commit d00a08fa70); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
Hawk/Lang/en-US.xaml:2042 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
Hawk/Lang/zh-CN.xaml:1193 | Possible generic-api-key secret in history (commit d00a08fa70); removed from the current tree but still retrievable | Secrets (gitleaks) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | ok | prov-4 | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 15 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | skipped | — | 0 | no registry dependencies declared |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 8 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 7 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | cc3560b4ca8f | prov-5+qual-2+sec-2 | 0% | 47 | 68 |
| 2026-11-14 | cc3560b4ca8f | prov-4+qual-2+sec-2 | 0% | 47 | 68 |
Full text report
- Repository: https://github.com/ferventdesert/Hawk
- Commit:
cc3560b4ca8f1efbd6323351ce1a67bc41d51ccb - Generated: 2026-11-14T14:52:04+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 | 47 | poor | 90% | 100% |
| Security | 68 | weak | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
- Explicitly attributed share (lower bound): 0.0%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 0.0%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2018-08 | 1,612 | 0% |
| 2018-09 | 1,503 | 0% |
| 2018-10 | 3,619 | 0% |
| 2018-11 | 1,413 | 0% |
| 2018-12 | 92 | 0% |
| 2019-01 | 2,212 | 0% |
| 2019-03 | 26 | 0% |
| 2019-05 | 6 | 0% |
| 2019-06 | 86 | 0% |
| 2019-07 | 266 | 0% |
| 2019-08 | 65 | 0% |
| 2019-12 | 56 | 0% |
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 13% of function code in complex or long functions; 15% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 67 |
| Duplication | 40 |
| Code smells (Opengrep) | 96 |
| Tests and CI | 0 |
| Documentation | 65 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 1,399; mean complexity 2.8, 90th percentile 6; 16 complex and 13 long functions
- Duplicated lines: 15.1% of 20,090 compared
- Tests: 0 test lines for 36,155 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- SmartETLTool::RefreshSamples in Hawk.ETL/Process/SmartETLTool.cs: complexity 46, 195 lines
- DataProcessManager::Init in Hawk.ETL/Managements/DataProcessManager.cs: complexity 37, 470 lines
- DataManager::Init in Hawk.ETL/Managements/DataManager.cs: complexity 33, 350 lines
- XPathAnalyzer::GetDiff in Hawk.ETL/Crawlers/XPathAnalyzer.cs: complexity 22, 40 lines
- XPathAnalyzer::GetDiff in Hawk.ETL/Crawlers/XPathx.cs: complexity 22, 40 lines
Security
Security posture is weak: 5 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 79 |
| Static analysis (Opengrep) | 89 |
| 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 |
|---|---|---|
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Hawk.Core/Connectors/MySQLConnector.cs:46 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Hawk.Core/Connectors/SQLServerConnector.cs:43 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Hawk.Core/Connectors/SQLiteConnector.cs:39 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Hawk.Core/Connectors/SQLiteConnector.cs:209 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Hawk.Core/Connectors/SQLiteConnector.cs:383 |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-binaryformatter-deserialization: The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is insecure and can't be made secure [confidence high] |
Hawk.Core/Utils/CustomSerializer.cs:31 |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-binaryformatter-deserialization: The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is insecure and can't be made secure [confidence high] |
Hawk.Core/Utils/CustomSerializer.cs:46 |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-binaryformatter-deserialization: The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is insecure and can't be made secure [confidence high] |
Hawk.Core/Utils/CustomSerializer.cs:61 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
Hawk.ETL/Plugins/Web/NlpTF.cs:28 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
Hawk.ETL/Plugins/Web/BaiduLocation.cs:17 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree |
Hawk/Lang/en-US.xaml:2042 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 8954d2cad1); removed from the current tree but still retrievable |
Hawk.Base/Plugins/Web/NlpTF.cs:24 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 8954d2cad1); removed from the current tree but still retrievable |
Hawk.Base/Plugins/Web/BaiduLocation.cs:12 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit d00a08fa70); removed from the current tree but still retrievable |
Hawk/Lang/DefaultLanguage.xaml:1193 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit d00a08fa70); removed from the current tree but still retrievable |
Hawk/Lang/zh-CN.xaml:1193 |
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 v5.2 ships Hawk5.2.zip (6526 downloads)
- binary-release-asset: release Hawk5.1 ships Hawk5.1.zip (1704 downloads)
- binary-release-asset: release v5.0 ships Hawk5.1.zip (59 downloads)
- binary-release-asset: release v5.0 ships Hawk5.zip (2391 downloads)
- binary-release-asset: release Hawk3 ships Hawk3_Release.zip (3005 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: 36,155; test lines: 0
| Language | Lines |
|---|---|
| C# | 35,891 |
| Python | 259 |
| Shell | 5 |