Executive summary
bee-san/Ares is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because it has pipeline tools referenced by a changeable name. It scores 63.3 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Security and Compliance, at 52.0, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5.8 points. Restricting the build's access tokens comes next, worth about 1.9 points. Raising Security and Compliance to 68 would lift the score to about 69.4.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two settings leave the servers or containers unsafe, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, correcting the unsafe settings and setting a waiting period for automatic updates would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 11,844 lines, about €14,000 to rebuild.
If Security and Compliance rose from 52.0 to 68, the lowest score rated Strong, the score would rise from 63.3 to about 69.4.
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 77 to 245 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,844 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 checkers.athena | 2 checkers.default_checker | 3 checkers.english | 4 checkers.lemmeknow_checker | 5 checkers.password | 6 checkers.regex_checker | 7 checkers.wait_athena | 8 checkers.wordlist | 9 cli | 10 cli.first_run | 11 cli_input_parser | 12 config | 13 decoders | 14 decoders.a1z26_decoder | 15 decoders.atbash_decoder | 16 decoders.base32_decoder | 17 decoders.base58_bitcoin_decoder | 18 decoders.base58_flickr_decoder | 19 decoders.base58_monero_decoder | 20 decoders.base58_ripple_decoder | 21 decoders.base64_decoder | 22 decoders.base65536_decoder | 23 decoders.base91_decoder | 24 decoders.binary_decoder | 25 decoders.braille_decoder | 26 decoders.brainfuck_interpreter | 27 decoders.caesar_decoder | 28 checkers.checker_type | 29 api_library_input_struct | 30 checkers.checker_result | 31 checkers | 32 checkers.human_checker | 33 decoders.interface | 34 decoders.crack_results | 35 ciphey | 36 storage.database | 37 cli_pretty_printing | 38 filtration_system | 39 searchers.astar | 40 searchers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 checkers.athena | ||||||||||||||||||||||||||||||||||||||||
| 2 checkers.default_checker | ||||||||||||||||||||||||||||||||||||||||
| 3 checkers.english | ||||||||||||||||||||||||||||||||||||||||
| 4 checkers.lemmeknow_checker | ||||||||||||||||||||||||||||||||||||||||
| 5 checkers.password | ||||||||||||||||||||||||||||||||||||||||
| 6 checkers.regex_checker | ||||||||||||||||||||||||||||||||||||||||
| 7 checkers.wait_athena | ||||||||||||||||||||||||||||||||||||||||
| 8 checkers.wordlist | ||||||||||||||||||||||||||||||||||||||||
| 9 cli | ||||||||||||||||||||||||||||||||||||||||
| 10 cli.first_run | ||||||||||||||||||||||||||||||||||||||||
| 11 cli_input_parser | ||||||||||||||||||||||||||||||||||||||||
| 12 config | ||||||||||||||||||||||||||||||||||||||||
| 13 decoders | ||||||||||||||||||||||||||||||||||||||||
| 14 decoders.a1z26_decoder | ||||||||||||||||||||||||||||||||||||||||
| 15 decoders.atbash_decoder | ||||||||||||||||||||||||||||||||||||||||
| 16 decoders.base32_decoder | ||||||||||||||||||||||||||||||||||||||||
| 17 decoders.base58_bitcoin_decoder | ||||||||||||||||||||||||||||||||||||||||
| 18 decoders.base58_flickr_decoder | ||||||||||||||||||||||||||||||||||||||||
| 19 decoders.base58_monero_decoder | ||||||||||||||||||||||||||||||||||||||||
| 20 decoders.base58_ripple_decoder | ||||||||||||||||||||||||||||||||||||||||
| 21 decoders.base64_decoder | ||||||||||||||||||||||||||||||||||||||||
| 22 decoders.base65536_decoder | ||||||||||||||||||||||||||||||||||||||||
| 23 decoders.base91_decoder | ||||||||||||||||||||||||||||||||||||||||
| 24 decoders.binary_decoder | ||||||||||||||||||||||||||||||||||||||||
| 25 decoders.braille_decoder | ||||||||||||||||||||||||||||||||||||||||
| 26 decoders.brainfuck_interpreter | ||||||||||||||||||||||||||||||||||||||||
| 27 decoders.caesar_decoder | ||||||||||||||||||||||||||||||||||||||||
| 28 checkers.checker_type | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 api_library_input_struct | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 checkers.checker_result | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 checkers | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 checkers.human_checker | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 decoders.interface | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 decoders.crack_results | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 ciphey | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 storage.database | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 cli_pretty_printing | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 filtration_system | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 searchers.astar | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 searchers | 1 | 1 |
28→30 checkers.checker_type uses checkers.checker_result part of a loop✕
- Connections
- 2 pairs of types, where a type in checkers.checker_type uses a type in checkers.checker_result.
- The types involved
ciphey.checkers.checker_type.Check→ciphey.checkers.checker_result.CheckResultciphey.checkers.checker_type.Checker→ciphey.checkers.checker_result.CheckResult
- Direction
- checkers.checker_type uses checkers.checker_result, so a change to checkers.checker_result can break checkers.checker_type, while a change to checkers.checker_type can't break checkers.checker_result.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→28 api_library_input_struct uses checkers.checker_type✕
- Connections
- 1 pair of types, where a type in api_library_input_struct uses a type in checkers.checker_type.
- The types involved
ciphey.api_library_input_struct.LibraryInput→ciphey.checkers.checker_type.Checker
- Direction
- api_library_input_struct uses checkers.checker_type, so a change to checkers.checker_type can break api_library_input_struct, while a change to api_library_input_struct can't break checkers.checker_type.
- Position
- Below the diagonal: api_library_input_struct uses a module listed above it, which is the healthy direction.
30→28 checkers.checker_result uses checkers.checker_type✕
- Connections
- 1 pair of types, where a type in checkers.checker_result uses a type in checkers.checker_type.
- The types involved
ciphey.checkers.checker_result.CheckResult→ciphey.checkers.checker_type.Checker
- Direction
- checkers.checker_result uses checkers.checker_type, so a change to checkers.checker_type can break checkers.checker_result, while a change to checkers.checker_result can't break checkers.checker_type.
- Position
- Below the diagonal: checkers.checker_result uses a module listed above it, which is the healthy direction.
31→30 checkers uses checkers.checker_result✕
- Connections
- 1 pair of types, where a type in checkers uses a type in checkers.checker_result.
- The types involved
ciphey.checkers.CheckerTypes→ciphey.checkers.checker_result.CheckResult
- Direction
- checkers uses checkers.checker_result, so a change to checkers.checker_result can break checkers, while a change to checkers can't break checkers.checker_result.
- Position
- Below the diagonal: checkers uses a module listed above it, which is the healthy direction.
32→30 checkers.human_checker uses checkers.checker_result✕
- Connections
- 1 pair of types, where a type in checkers.human_checker uses a type in checkers.checker_result.
- The types involved
ciphey.checkers.human_checker.human_checker$module→ciphey.checkers.checker_result.CheckResult
- Direction
- checkers.human_checker uses checkers.checker_result, so a change to checkers.checker_result can break checkers.human_checker, while a change to checkers.human_checker can't break checkers.checker_result.
- Position
- Below the diagonal: checkers.human_checker uses a module listed above it, which is the healthy direction.
33→31 decoders.interface uses checkers✕
- Connections
- 2 pairs of types, where a type in decoders.interface uses a type in checkers.
- The types involved
ciphey.decoders.interface.Crack→ciphey.checkers.CheckerTypesciphey.decoders.interface.Decoder→ciphey.checkers.CheckerTypes
- Direction
- decoders.interface uses checkers, so a change to checkers can break decoders.interface, while a change to decoders.interface can't break checkers.
- Position
- Below the diagonal: decoders.interface uses a module listed above it, which is the healthy direction.
33→34 decoders.interface uses decoders.crack_results part of a loop✕
- Connections
- 2 pairs of types, where a type in decoders.interface uses a type in decoders.crack_results.
- The types involved
ciphey.decoders.interface.Crack→ciphey.decoders.crack_results.CrackResultciphey.decoders.interface.Decoder→ciphey.decoders.crack_results.CrackResult
- Direction
- decoders.interface uses decoders.crack_results, so a change to decoders.crack_results can break decoders.interface, while a change to decoders.interface can't break decoders.crack_results.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→30 decoders.crack_results uses checkers.checker_result✕
- Connections
- 1 pair of types, where a type in decoders.crack_results uses a type in checkers.checker_result.
- The types involved
ciphey.decoders.crack_results.CrackResult→ciphey.checkers.checker_result.CheckResult
- Direction
- decoders.crack_results uses checkers.checker_result, so a change to checkers.checker_result can break decoders.crack_results, while a change to decoders.crack_results can't break checkers.checker_result.
- Position
- Below the diagonal: decoders.crack_results uses a module listed above it, which is the healthy direction.
34→33 decoders.crack_results uses decoders.interface✕
- Connections
- 1 pair of types, where a type in decoders.crack_results uses a type in decoders.interface.
- The types involved
ciphey.decoders.crack_results.CrackResult→ciphey.decoders.interface.Decoder
- Direction
- decoders.crack_results uses decoders.interface, so a change to decoders.interface can break decoders.crack_results, while a change to decoders.crack_results can't break decoders.interface.
- Position
- Below the diagonal: decoders.crack_results uses a module listed above it, which is the healthy direction.
35→12 ciphey uses config✕
- Connections
- 1 pair of types, where a type in ciphey uses a type in config.
- The types involved
ciphey.ciphey$module→ciphey.config.Config
- Direction
- ciphey uses config, so a change to config can break ciphey, while a change to ciphey can't break config.
- Position
- Below the diagonal: ciphey uses a module listed above it, which is the healthy direction.
35→30 ciphey uses checkers.checker_result✕
- Connections
- 1 pair of types, where a type in ciphey uses a type in checkers.checker_result.
- The types involved
ciphey.ciphey$module→ciphey.checkers.checker_result.CheckResult
- Direction
- ciphey uses checkers.checker_result, so a change to checkers.checker_result can break ciphey, while a change to ciphey can't break checkers.checker_result.
- Position
- Below the diagonal: ciphey uses a module listed above it, which is the healthy direction.
35→34 ciphey uses decoders.crack_results✕
- Connections
- 1 pair of types, where a type in ciphey uses a type in decoders.crack_results.
- The types involved
ciphey.DecoderResult→ciphey.decoders.crack_results.CrackResult
- Direction
- ciphey uses decoders.crack_results, so a change to decoders.crack_results can break ciphey, while a change to ciphey can't break decoders.crack_results.
- Position
- Below the diagonal: ciphey uses a module listed above it, which is the healthy direction.
36→30 storage.database uses checkers.checker_result✕
- Connections
- 1 pair of types, where a type in storage.database uses a type in checkers.checker_result.
- The types involved
ciphey.storage.database.database$module→ciphey.checkers.checker_result.CheckResult
- Direction
- storage.database uses checkers.checker_result, so a change to checkers.checker_result can break storage.database, while a change to storage.database can't break checkers.checker_result.
- Position
- Below the diagonal: storage.database uses a module listed above it, which is the healthy direction.
36→34 storage.database uses decoders.crack_results✕
- Connections
- 1 pair of types, where a type in storage.database uses a type in decoders.crack_results.
- The types involved
ciphey.storage.database.CacheEntry→ciphey.decoders.crack_results.CrackResult
- Direction
- storage.database uses decoders.crack_results, so a change to decoders.crack_results can break storage.database, while a change to storage.database can't break decoders.crack_results.
- Position
- Below the diagonal: storage.database uses a module listed above it, which is the healthy direction.
37→35 cli_pretty_printing uses ciphey✕
- Connections
- 1 pair of types, where a type in cli_pretty_printing uses a type in ciphey.
- The types involved
ciphey.cli_pretty_printing.cli_pretty_printing$module→ciphey.DecoderResult
- Direction
- cli_pretty_printing uses ciphey, so a change to ciphey can break cli_pretty_printing, while a change to cli_pretty_printing can't break ciphey.
- Position
- Below the diagonal: cli_pretty_printing uses a module listed above it, which is the healthy direction.
38→31 filtration_system uses checkers✕
- Connections
- 1 pair of types, where a type in filtration_system uses a type in checkers.
- The types involved
ciphey.filtration_system.Decoders→ciphey.checkers.CheckerTypes
- Direction
- filtration_system uses checkers, so a change to checkers can break filtration_system, while a change to filtration_system can't break checkers.
- Position
- Below the diagonal: filtration_system uses a module listed above it, which is the healthy direction.
38→34 filtration_system uses decoders.crack_results✕
- Connections
- 1 pair of types, where a type in filtration_system uses a type in decoders.crack_results.
- The types involved
ciphey.filtration_system.MyResults→ciphey.decoders.crack_results.CrackResult
- Direction
- filtration_system uses decoders.crack_results, so a change to decoders.crack_results can break filtration_system, while a change to filtration_system can't break decoders.crack_results.
- Position
- Below the diagonal: filtration_system uses a module listed above it, which is the healthy direction.
38→35 filtration_system uses ciphey✕
- Connections
- 1 pair of types, where a type in filtration_system uses a type in ciphey.
- The types involved
ciphey.filtration_system.filtration_system$module→ciphey.DecoderResult
- Direction
- filtration_system uses ciphey, so a change to ciphey can break filtration_system, while a change to filtration_system can't break ciphey.
- Position
- Below the diagonal: filtration_system uses a module listed above it, which is the healthy direction.
39→35 searchers.astar uses ciphey✕
- Connections
- 1 pair of types, where a type in searchers.astar uses a type in ciphey.
- The types involved
ciphey.searchers.astar.AStarNode→ciphey.DecoderResult
- Direction
- searchers.astar uses ciphey, so a change to ciphey can break searchers.astar, while a change to searchers.astar can't break ciphey.
- Position
- Below the diagonal: searchers.astar uses a module listed above it, which is the healthy direction.
40→35 searchers uses ciphey✕
- Connections
- 1 pair of types, where a type in searchers uses a type in ciphey.
- The types involved
ciphey.searchers.searchers$module→ciphey.DecoderResult
- Direction
- searchers uses ciphey, so a change to ciphey can break searchers, while a change to searchers can't break ciphey.
- Position
- Below the diagonal: searchers uses a module listed above it, which is the healthy direction.
40→38 searchers uses filtration_system✕
- Connections
- 1 pair of types, where a type in searchers uses a type in filtration_system.
- The types involved
ciphey.searchers.searchers$module→ciphey.filtration_system.MyResults
- Direction
- searchers uses filtration_system, so a change to filtration_system can break searchers, while a change to searchers can't break filtration_system.
- Position
- Below the diagonal: searchers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 51 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 44 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; Reconcile the README with reality: docs/README.md links to `ciphey_overview.md`, but `docs/ciphey_overview.md` does not exist; docs/README.md links to `ciphey_architecture.md`, but `docs/ciphey_architecture.md` does not exist; docs/README.md links to `using_ciphey.md`, but `docs/using_ciphey.md` does not exist; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +5.8 pts | Low | ADR Quality |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| Reconcile the README with reality: docs/README.md links to `ciphey_overview.md`, but `docs/ciphey_overview.md` does not exist; docs/README.md links to `ciphey_architecture.md`, but `docs/ciphey_architecture.md` does not exist; docs/README.md links to `using_ciphey.md`, but `docs/using_ciphey.md` does not exist. | +3.4 pts | Medium | Documentation accuracy |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). | +1.5 pts | Low | IaC & Container Security |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.6 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/cli_pretty_printing/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/checkers/athena.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/searchers/mod.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/searchers/astar.rs | 7.1 | Near-clean | Cyclomatic Complexity: ciphey::searchers::astar::expand_node (cyclomatic 26) |
| src/cli/first_run.rs | 7.1 | Near-clean | God Classes: FunctionTooLong: ciphey::cli::first_run::run_first_time_setup |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/decoders/binary_decoder.rs | 7.8 | Near-clean | Code Duplication: Edited copies of one member (4 members, 29+ corresponding lines) |
| src/storage/database.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (38 corresponding lines) |
| src/decoders/base58_bitcoin_decoder.rs | 7.8 | Near-clean | Code Duplication: Edited copies of one member (3 members, 10+ corresponding lines) |
| src/decoders/a1z26_decoder.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| tests/integration_test.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 44 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 196 of 208 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 44 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (11844 LoC, 99 module-visible types across 11 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 45 commits in the last 90 days, yet 47 of 50 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was ciphey::searchers::astar::expand_node at 26. A further 1 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ciphey::decoders::morse_code::morse_to_alphanumeric at 57 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/decoders/morse_code.rs (ciphey::decoders::morse_code::morse_to_alphanumeric at 57). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ciphey::searchers::astar::expand_node (cyclomatic 26), ciphey::searchers::astar::astar (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 function(s) exceeded the cognitive complexity threshold of 15; the worst was ciphey::searchers::astar::astar at 79.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with ciphey::searchers::astar::astar (cognitive 79), ciphey::searchers::astar::expand_node (cognitive 71). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.7 to about 8.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with astar.rs (2), first_run.rs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 7.1 % of the production lines (837 of 11,844) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copies of one member (3 members, 10+ corresponding lines) finding(s) in Code Duplication — start with base58_bitcoin_decoder.rs, atbash_decoder.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with a1z26_decoder.rs, binary_decoder.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with athena.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D12 · Dependency Hygiene
5 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 482 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/config/mod.rs. Counted over 50 of the 58 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
16 deducted task-comment markers across 11844 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 16 TodoComment finding(s) in Explicit Debt — start with mod.rs (2), athena.rs (2), integration_test.rs. — One of this dimension's main actionable groups (16 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 47 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
51 finding(s): 0 critical, 33 high, 18 medium, 0 low. 28 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `images/better_demo.cast` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 28 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (28 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
36 finding(s): 1 critical, 0 high, 35 medium, 0 low.
What to do
- Resolve the 15 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 11 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `human_checker_check` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/cli_pretty_printing/mod.rs:387
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/README.md links to `ciphey_overview.md`, but `docs/ciphey_overview.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:9
- docs/README.md links to `ciphey_architecture.md`, but `docs/ciphey_architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:14
- docs/README.md links to `using_ciphey.md`, but `docs/using_ciphey.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:49
What to do
- Reconcile the README with reality: docs/README.md links to `ciphey_overview.md`, but `docs/ciphey_overview.md` does not exist; docs/README.md links to `ciphey_architecture.md`, but `docs/ciphey_architecture.md` does not exist; docs/README.md links to `using_ciphey.md`, but `docs/using_ciphey.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
- `Config.lemmeknow_min_rarity` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Its value is copied into `min_rarity`, and nothing reads that either. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config/mod.rs:33
- `Config.lemmeknow_max_rarity` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Its value is copied into `max_rarity`, and nothing reads that either. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config/mod.rs:36
- `Config.lemmeknow_boundaryless` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Its value is copied into `boundaryless`, and nothing reads that either. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config/mod.rs:45
- `Config.model_path` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config/mod.rs:71
- `TempCrackResult.encrypted_text` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/decoders/crack_results.rs:78
- `TempCrackResult.key` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/decoders/crack_results.rs:88
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X5 · Nullable reference types
- `dirs::home_dir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get_test_dir_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/lib.rs:324
- `std::fs::create_dir_all(&path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `set_test_db_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/lib.rs:334
- `dirs::home_dir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get_database_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/storage/database.rs:92
- `serde_json::to_string(&path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `insert_cache` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/storage/database.rs:198
- `result_sender.send(Some(node.state.clone()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `astar` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/searchers/astar.rs:568
- `result_sender.send(None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `astar` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/searchers/astar.rs:621
- `result_sender.send(Some(result_text))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `bfs` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/searchers/bfs.rs:52
- `handle.join()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `search_for_plaintext` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/searchers/mod.rs:79, src/searchers/mod.rs:88
- `s.send(results.clone())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `run` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/filtration_system/mod.rs:73, src/filtration_system/mod.rs:82
- `Regex::new(r"[0-9]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `decode_a1z26` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/a1z26_decoder.rs:98
- `Regex::new(r"\A([0-9,;:\-\s])*\z")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `decode_a1z26` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/a1z26_decoder.rs:103
- `Regex::new(r"[,;:\-\s]+")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `decode_a1z26` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/a1z26_decoder.rs:108
- `TempCrackResult::deserialize(deserializer)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `deserialize` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/crack_results.rs:95
- `std::str::from_utf8(pair)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `hexadecimal_to_string` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/hexadecimal_decoder.rs:104
- `u8::from_str_radix(std::str::from_utf8(pair).unwrap(),16)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `hexadecimal_to_string` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/hexadecimal_decoder.rs:104
- `Regex::new(r"\s+")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `crack` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/decoders/morse_code.rs:38
- `dirs::home_dir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get_config_file_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/config/mod.rs:166
- `fs::create_dir_all(&path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get_config_file_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/config/mod.rs:168
- `toml::from_str(contents)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `parse_toml_with_unknown_keys` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/config/mod.rs:205, src/config/mod.rs:235
- `toml::to_string_pretty(config)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `save_config_to_file` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/config/mod.rs:385
- `File::create(path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `save_config_to_file` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/config/mod.rs:386
- `file.write_all(toml_string.as_bytes())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `save_config_to_file` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/config/mod.rs:388
- `write(file_path,&plaintext[0])` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `program_exiting_successful_decoding` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli_pretty_printing/mod.rs:343
- `std::io::stdin().read_line(&mut input)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `display_top_results` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli_pretty_printing/mod.rs:530
- `std::io::stdin().read_line(&mut file_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `display_top_results` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli_pretty_printing/mod.rs:545
- `io::stdout().flush()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `run_first_time_setup` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:443
- `io::stdout().flush()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `ask_yes_no_question` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:495
- `io::stdin().read_line(&mut input)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `ask_yes_no_question` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:498
- `io::stdout().flush()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get_user_input_range` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:532
- `io::stdin().read_line(&mut input)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get_user_input_range` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:535
- `io::stdout().flush()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get_user_input_rgb` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:563
- `io::stdin().read_line(&mut input)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get_user_input_rgb` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:566
- `std::io::stdin().read_line(&mut input)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get_wordlist_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/cli/first_run.rs:632
- `regex_to_parse` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `check` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/checkers/regex_checker.rs:34
- `Regex::new(®ex_to_parse.unwrap())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `check` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/checkers/regex_checker.rs:34
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 88.2 | Exemplary | Solid. |
| Architecture | 98.9 | Exemplary | Strongest area. |
| Maturity | 61.9 | Adequate | Acceptable, with room to improve. |
| Readiness | 80.9 | Strong | Solid. |
| Security | 52.0 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 80.0 | Strong | Solid. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — [0m - FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1) REDACTED:10 -------------------- 8 | COPY src/ src/ 9 | COPY benches/ benches/ 10 | >>> RUN cargo build --release 11 | 12 | FROM alpine:3.12 -------------------- ERROR: failed to solve: process "/bin/sh -c cargo build --release" did not complete successfully: exit code: 101; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 101 (`/bin/sh -c cargo build --release`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 101 (`/bin/sh -c cargo build --release`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~410 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (733 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 57 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 37 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: wav
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 156 finding(s)
- Symbol treated as nullable, then dereferenced unguarded src/lib.rs:324
- Symbol treated as nullable, then dereferenced unguarded src/lib.rs:334
- Symbol treated as nullable, then dereferenced unguarded src/storage/database.rs:92
- Symbol treated as nullable, then dereferenced unguarded src/storage/database.rs:198
- Symbol treated as nullable, then dereferenced unguarded src/searchers/astar.rs:568
- Symbol treated as nullable, then dereferenced unguarded src/searchers/astar.rs:621
- Symbol treated as nullable, then dereferenced unguarded src/searchers/bfs.rs:52
- Symbol treated as nullable, then dereferenced unguarded src/searchers/mod.rs:79
- Symbol treated as nullable, then dereferenced unguarded src/searchers/mod.rs:88
- Symbol treated as nullable, then dereferenced unguarded src/filtration_system/mod.rs:73
- Symbol treated as nullable, then dereferenced unguarded src/filtration_system/mod.rs:82
- Symbol treated as nullable, then dereferenced unguarded src/decoders/a1z26_decoder.rs:98
- Symbol treated as nullable, then dereferenced unguarded src/decoders/a1z26_decoder.rs:103
- Symbol treated as nullable, then dereferenced unguarded src/decoders/a1z26_decoder.rs:108
- Symbol treated as nullable, then dereferenced unguarded src/decoders/crack_results.rs:95
- Symbol treated as nullable, then dereferenced unguarded src/decoders/hexadecimal_decoder.rs:104
- Symbol treated as nullable, then dereferenced unguarded src/decoders/hexadecimal_decoder.rs:104
- Symbol treated as nullable, then dereferenced unguarded src/decoders/morse_code.rs:38
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:166
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:168
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:205
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:235
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:385
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:386
- Symbol treated as nullable, then dereferenced unguarded src/config/mod.rs:388
- TodoComment tests/integration_test.rs:14
- TodoComment src/lib.rs:417
- TodoComment src/main.rs:14
- TodoComment src/searchers/bfs.rs:75
- TodoComment src/searchers/helper_functions.rs:31
- TodoComment src/searchers/mod.rs:149
- TodoComment src/decoders/base32_decoder.rs:158
- TodoComment src/decoders/interface.rs:6
- TodoComment src/decoders/morse_code.rs:33
- TodoComment src/cli_pretty_printing/mod.rs:371
- TodoComment src/checkers/athena.rs:25
- TodoComment src/checkers/lemmeknow_checker.rs:13
- TodoComment src/checkers/athena.rs:88
- TodoComment src/checkers/english.rs:78
- TodoComment src/checkers/human_checker.rs:34
- TodoComment src/checkers/regex_checker.rs:31
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ciphey::searchers::astar::astar (cognitive 79) src/searchers/astar.rs:445
- ciphey::searchers::astar::expand_node (cognitive 71) src/searchers/astar.rs:188
- ciphey::decoders::vigenere_decoder::break_vigenere (cognitive 26) src/decoders/vigenere_decoder.rs:143
- ciphey::cli_pretty_printing::display_top_results (cognitive 21) src/cli_pretty_printing/mod.rs:503
- ciphey::config::get_config_file_into_struct (cognitive 19) src/config/mod.rs:308
- ciphey::perform_cracking (cognitive 17) src/lib.rs:101
- ciphey::searchers::search_for_plaintext (cognitive 16) src/searchers/mod.rs:44
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Configuration option is read nowhere src/config/mod.rs:33
- Configuration option is read nowhere src/config/mod.rs:36
- Configuration option is read nowhere src/config/mod.rs:45
- Configuration option is read nowhere src/config/mod.rs:71
- Configuration option is read nowhere src/decoders/crack_results.rs:78
- Configuration option is read nowhere src/decoders/crack_results.rs:88
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: ciphey::cli::first_run::run_first_time_setup src/cli/first_run.rs:215
- FunctionTooLong: ciphey::searchers::astar::expand_node src/searchers/astar.rs:188
- FunctionTooLong: ciphey::searchers::astar::astar src/searchers/astar.rs:445
- REDACTED
- REDACTED
- REDACTED
- ciphey::searchers::astar::expand_node (cyclomatic 26) src/searchers/astar.rs:188
- ciphey::searchers::astar::astar (cyclomatic 21) src/searchers/astar.rs:445
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 10+ corresponding lines) src/decoders/base58_bitcoin_decoder.rs:36
- Edited copies of one member (3 members, 10+ corresponding lines) src/decoders/atbash_decoder.rs:14
- Edited copy of a member (10 corresponding lines) src/decoders/a1z26_decoder.rs:15
- Edited copy of a member (10 corresponding lines) src/decoders/binary_decoder.rs:14
- Duplicated block (11 lines × 2) src/checkers/athena.rs:59
- Duplicated block (11 lines × 2) src/cli_pretty_printing/mod.rs:75
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (4 members, 29+ corresponding lines) src/decoders/binary_decoder.rs:28
- Edited copy of a member (38 corresponding lines) src/storage/database.rs:185
- Edited copy of a member (29 corresponding lines) src/decoders/citrix_ctx1_decoder.rs:41
- Edited copies of one member (3 members, 11+ corresponding lines) src/cli/first_run.rs:114
- Edited copy of a member (19 corresponding lines) src/storage/database.rs:335
- Edited copies of one member (7 members, 14+ corresponding lines) src/checkers/athena.rs:23
- Edited copies of one member (5 members, 8+ corresponding lines) src/decoders/base58_bitcoin_decoder.rs:95
- Edited copy of a member (6 corresponding lines) src/lib.rs:323
- Duplicated block (12 lines × 5) src/checkers/wait_athena.rs:50
- Duplicated block (9–10 lines × 2) src/checkers/athena.rs:41
- Duplicated block (6 lines × 3) src/cli/first_run.rs:119
- Duplicated block (6 lines × 2) src/cli/first_run.rs:532
- Duplicated block (5 lines × 3) src/cli/first_run.rs:494
- Duplicated block (14 lines × 13) src/decoders/a1z26_decoder.rs:57
- Duplicated block (11 lines × 3) src/decoders/caesar_decoder.rs:64
- Duplicated block (10 lines × 4) src/checkers/athena.rs:67
- Duplicated block (5 lines × 4) src/cli/first_run.rs:253
- Empty method body — does nothing with its inputs src/cli_pretty_printing/mod.rs:387
Minor — 10 finding(s)
- README/code drift docs/README.md:9
- README/code drift docs/README.md:14
- README/code drift docs/README.md:49
- Off-boarding risk: anonymized user #1
- No ADRs found Cargo.toml:16
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Dependabot does not watch github-actions REDACTED:7
Minor — 5 finding(s)
- Outdated: log
- Outdated: rand
- Outdated: rpassword
- Outdated: toml
- Outdated: uuid
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-d212f29d3123470db82a96fd3d9d1b09/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-d212f29d3123470db82a96fd3d9d1b09/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=26" --report-format json --report-path /tmp/watchdog-gitleaks-d212f29d3123470db82a96fd3d9d1b09/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d212f29d3123470db82a96fd3d9d1b09/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 51 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 36 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |