Executive summary
bestvibes/exiftoolwrapper-android falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 56.9 out of 100 and is rated Adequate, and all 22 of its critical findings are security problems in the build pipeline and in its code.
Production Readiness, at 40.5, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6.4 points. Adding automated security scanning would lift Production Readiness itself, worth about 8.5 points. Raising Production Readiness to 70 would lift the score to about 68.2.
Eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two weaknesses in the code could be used by an attacker. Pinning each tool to an exact version and fixing the weaknesses the scanner points to would close both risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.
The product code is 2,360 lines, about €2,800 to rebuild.
If Production Readiness rose from 40.5 to 70, the lowest score rated Strong, the score would rise from 56.9 to about 68.2.
Rebuild cost: about €2,800 · Estimate
| Cost to rebuild | €930 to €4,700, for 15 to 49 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.8 at a score of 57. 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: 2,360 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 CommandHistory | 2 CommandParser | 3 CommandRunner.PreviewToken.CompositeUnbound | 4 DisclaimerPrefs | 5 FileUtils | 6 MainActivity | 7 Token.Composite | 8 CommandRunner | 9 UserPresets | 10 me.bestvibes.exiftoolwrapper | 11 CommandRunner.Outcome | 12 CommandParser.Result | 13 CommandRunner.PreviewToken | 14 CommandRunner.PreviewToken.CompositeUnbound.Either | 15 SlotCount | 16 SlotRole | 17 Token | 18 Token.Composite.Part |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 CommandHistory | ||||||||||||||||||
| 2 CommandParser | ||||||||||||||||||
| 3 CommandRunner.PreviewToken.CompositeUnbound | ||||||||||||||||||
| 4 DisclaimerPrefs | ||||||||||||||||||
| 5 FileUtils | ||||||||||||||||||
| 6 MainActivity | ||||||||||||||||||
| 7 Token.Composite | ||||||||||||||||||
| 8 CommandRunner | 1 | |||||||||||||||||
| 9 UserPresets | 1 | |||||||||||||||||
| 10 me.bestvibes.exiftoolwrapper | 1 | 4 | 2 | |||||||||||||||
| 11 CommandRunner.Outcome | 2 | |||||||||||||||||
| 12 CommandParser.Result | 2 | 1 | ||||||||||||||||
| 13 CommandRunner.PreviewToken | 1 | 3 | 1 | |||||||||||||||
| 14 CommandRunner.PreviewToken.CompositeUnbound.Either | 2 | 1 | ||||||||||||||||
| 15 SlotCount | 2 | |||||||||||||||||
| 16 SlotRole | 4 | |||||||||||||||||
| 17 Token | 1 | 3 | ||||||||||||||||
| 18 Token.Composite.Part | 2 | 1 |
8→10 CommandRunner uses me.bestvibes.exiftoolwrapper part of a loop✕
- Connections
- 1 pair of types, where a type in CommandRunner uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.SlotBinding→me.bestvibes.exiftoolwrapper.FileSlot
- Direction
- CommandRunner uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break CommandRunner, while a change to CommandRunner can't break me.bestvibes.exiftoolwrapper.
- 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.
9→10 UserPresets uses me.bestvibes.exiftoolwrapper part of a loop✕
- Connections
- 1 pair of types, where a type in UserPresets uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.UserPresets.Saved→me.bestvibes.exiftoolwrapper.Command
- Direction
- UserPresets uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break UserPresets, while a change to UserPresets can't break me.bestvibes.exiftoolwrapper.
- 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.
10→2 me.bestvibes.exiftoolwrapper uses CommandParser✕
- Connections
- 1 pair of types, where a type in me.bestvibes.exiftoolwrapper uses a type in CommandParser.
- The types involved
me.bestvibes.exiftoolwrapper.CommandParser→me.bestvibes.exiftoolwrapper.CommandParser.Result
- Direction
- me.bestvibes.exiftoolwrapper uses CommandParser, so a change to CommandParser can break me.bestvibes.exiftoolwrapper, while a change to me.bestvibes.exiftoolwrapper can't break CommandParser.
- Position
- Below the diagonal: me.bestvibes.exiftoolwrapper uses a module listed above it, which is the healthy direction.
10→8 me.bestvibes.exiftoolwrapper uses CommandRunner✕
- Connections
- 4 pairs of types, where a type in me.bestvibes.exiftoolwrapper uses a type in CommandRunner.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner→me.bestvibes.exiftoolwrapper.CommandRunner.Outcomeme.bestvibes.exiftoolwrapper.CommandRunner→me.bestvibes.exiftoolwrapper.CommandRunner.Previewme.bestvibes.exiftoolwrapper.CommandRunner→me.bestvibes.exiftoolwrapper.CommandRunner.SlotBindingme.bestvibes.exiftoolwrapper.MainActivity→me.bestvibes.exiftoolwrapper.CommandRunner.SlotBinding
- Direction
- me.bestvibes.exiftoolwrapper uses CommandRunner, so a change to CommandRunner can break me.bestvibes.exiftoolwrapper, while a change to me.bestvibes.exiftoolwrapper can't break CommandRunner.
- Position
- Below the diagonal: me.bestvibes.exiftoolwrapper uses a module listed above it, which is the healthy direction.
10→9 me.bestvibes.exiftoolwrapper uses UserPresets✕
- Connections
- 2 pairs of types, where a type in me.bestvibes.exiftoolwrapper uses a type in UserPresets.
- The types involved
me.bestvibes.exiftoolwrapper.MainActivity→me.bestvibes.exiftoolwrapper.UserPresets.Savedme.bestvibes.exiftoolwrapper.UserPresets→me.bestvibes.exiftoolwrapper.UserPresets.Saved
- Direction
- me.bestvibes.exiftoolwrapper uses UserPresets, so a change to UserPresets can break me.bestvibes.exiftoolwrapper, while a change to me.bestvibes.exiftoolwrapper can't break UserPresets.
- Position
- Below the diagonal: me.bestvibes.exiftoolwrapper uses a module listed above it, which is the healthy direction.
11→8 CommandRunner.Outcome uses CommandRunner✕
- Connections
- 2 pairs of types, where a type in CommandRunner.Outcome uses a type in CommandRunner.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.Outcome.Failure→me.bestvibes.exiftoolwrapper.CommandRunner.Outcomeme.bestvibes.exiftoolwrapper.CommandRunner.Outcome.Success→me.bestvibes.exiftoolwrapper.CommandRunner.Outcome
- Direction
- CommandRunner.Outcome uses CommandRunner, so a change to CommandRunner can break CommandRunner.Outcome, while a change to CommandRunner.Outcome can't break CommandRunner.
- Position
- Below the diagonal: CommandRunner.Outcome uses a module listed above it, which is the healthy direction.
12→2 CommandParser.Result uses CommandParser✕
- Connections
- 2 pairs of types, where a type in CommandParser.Result uses a type in CommandParser.
- The types involved
me.bestvibes.exiftoolwrapper.CommandParser.Result.Ok→me.bestvibes.exiftoolwrapper.CommandParser.Resultme.bestvibes.exiftoolwrapper.CommandParser.Result.Rejected→me.bestvibes.exiftoolwrapper.CommandParser.Result
- Direction
- CommandParser.Result uses CommandParser, so a change to CommandParser can break CommandParser.Result, while a change to CommandParser.Result can't break CommandParser.
- Position
- Below the diagonal: CommandParser.Result uses a module listed above it, which is the healthy direction.
12→10 CommandParser.Result uses me.bestvibes.exiftoolwrapper✕
- Connections
- 1 pair of types, where a type in CommandParser.Result uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.CommandParser.Result.Ok→me.bestvibes.exiftoolwrapper.Command
- Direction
- CommandParser.Result uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break CommandParser.Result, while a change to CommandParser.Result can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: CommandParser.Result uses a module listed above it, which is the healthy direction.
13→3 CommandRunner.PreviewToken uses CommandRunner.PreviewToken.CompositeUnbound✕
- Connections
- 1 pair of types, where a type in CommandRunner.PreviewToken uses a type in CommandRunner.PreviewToken.CompositeUnbound.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound→me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound.Either
- Direction
- CommandRunner.PreviewToken uses CommandRunner.PreviewToken.CompositeUnbound, so a change to CommandRunner.PreviewToken.CompositeUnbound can break CommandRunner.PreviewToken, while a change to CommandRunner.PreviewToken can't break CommandRunner.PreviewToken.CompositeUnbound.
- Position
- Below the diagonal: CommandRunner.PreviewToken uses a module listed above it, which is the healthy direction.
13→8 CommandRunner.PreviewToken uses CommandRunner✕
- Connections
- 3 pairs of types, where a type in CommandRunner.PreviewToken uses a type in CommandRunner.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.Bound→me.bestvibes.exiftoolwrapper.CommandRunner.PreviewTokenme.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound→me.bestvibes.exiftoolwrapper.CommandRunner.PreviewTokenme.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.Unbound→me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken
- Direction
- CommandRunner.PreviewToken uses CommandRunner, so a change to CommandRunner can break CommandRunner.PreviewToken, while a change to CommandRunner.PreviewToken can't break CommandRunner.
- Position
- Below the diagonal: CommandRunner.PreviewToken uses a module listed above it, which is the healthy direction.
13→10 CommandRunner.PreviewToken uses me.bestvibes.exiftoolwrapper✕
- Connections
- 1 pair of types, where a type in CommandRunner.PreviewToken uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.Unbound→me.bestvibes.exiftoolwrapper.SlotKey
- Direction
- CommandRunner.PreviewToken uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break CommandRunner.PreviewToken, while a change to CommandRunner.PreviewToken can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: CommandRunner.PreviewToken uses a module listed above it, which is the healthy direction.
14→3 CommandRunner.PreviewToken.CompositeUnbound.Either uses CommandRunner.PreviewToken.CompositeUnbound✕
- Connections
- 2 pairs of types, where a type in CommandRunner.PreviewToken.CompositeUnbound.Either uses a type in CommandRunner.PreviewToken.CompositeUnbound.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound.Either.Slot→me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound.Eitherme.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound.Either.Text→me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound.Either
- Direction
- CommandRunner.PreviewToken.CompositeUnbound.Either uses CommandRunner.PreviewToken.CompositeUnbound, so a change to CommandRunner.PreviewToken.CompositeUnbound can break CommandRunner.PreviewToken.CompositeUnbound.Either, while a change to CommandRunner.PreviewToken.CompositeUnbound.Either can't break CommandRunner.PreviewToken.CompositeUnbound.
- Position
- Below the diagonal: CommandRunner.PreviewToken.CompositeUnbound.Either uses a module listed above it, which is the healthy direction.
14→10 CommandRunner.PreviewToken.CompositeUnbound.Either uses me.bestvibes.exiftoolwrapper✕
- Connections
- 1 pair of types, where a type in CommandRunner.PreviewToken.CompositeUnbound.Either uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.CommandRunner.PreviewToken.CompositeUnbound.Either.Slot→me.bestvibes.exiftoolwrapper.SlotKey
- Direction
- CommandRunner.PreviewToken.CompositeUnbound.Either uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break CommandRunner.PreviewToken.CompositeUnbound.Either, while a change to CommandRunner.PreviewToken.CompositeUnbound.Either can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: CommandRunner.PreviewToken.CompositeUnbound.Either uses a module listed above it, which is the healthy direction.
15→10 SlotCount uses me.bestvibes.exiftoolwrapper✕
- Connections
- 2 pairs of types, where a type in SlotCount uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.SlotCount.MANY→me.bestvibes.exiftoolwrapper.SlotCountme.bestvibes.exiftoolwrapper.SlotCount.ONE→me.bestvibes.exiftoolwrapper.SlotCount
- Direction
- SlotCount uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break SlotCount, while a change to SlotCount can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: SlotCount uses a module listed above it, which is the healthy direction.
16→10 SlotRole uses me.bestvibes.exiftoolwrapper✕
- Connections
- 4 pairs of types, where a type in SlotRole uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.SlotRole.Companion→me.bestvibes.exiftoolwrapper.SlotRoleme.bestvibes.exiftoolwrapper.SlotRole.SIDECAR→me.bestvibes.exiftoolwrapper.SlotRoleme.bestvibes.exiftoolwrapper.SlotRole.SOURCE→me.bestvibes.exiftoolwrapper.SlotRoleme.bestvibes.exiftoolwrapper.SlotRole.TARGET→me.bestvibes.exiftoolwrapper.SlotRole
- Direction
- SlotRole uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break SlotRole, while a change to SlotRole can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: SlotRole uses a module listed above it, which is the healthy direction.
17→7 Token uses Token.Composite✕
- Connections
- 1 pair of types, where a type in Token uses a type in Token.Composite.
- The types involved
me.bestvibes.exiftoolwrapper.Token.Composite→me.bestvibes.exiftoolwrapper.Token.Composite.Part
- Direction
- Token uses Token.Composite, so a change to Token.Composite can break Token, while a change to Token can't break Token.Composite.
- Position
- Below the diagonal: Token uses a module listed above it, which is the healthy direction.
17→10 Token uses me.bestvibes.exiftoolwrapper✕
- Connections
- 3 pairs of types, where a type in Token uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.Token.Composite→me.bestvibes.exiftoolwrapper.Tokenme.bestvibes.exiftoolwrapper.Token.SlotRef→me.bestvibes.exiftoolwrapper.SlotKeyme.bestvibes.exiftoolwrapper.Token.Standalone→me.bestvibes.exiftoolwrapper.Token
- Direction
- Token uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break Token, while a change to Token can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: Token uses a module listed above it, which is the healthy direction.
18→7 Token.Composite.Part uses Token.Composite✕
- Connections
- 2 pairs of types, where a type in Token.Composite.Part uses a type in Token.Composite.
- The types involved
me.bestvibes.exiftoolwrapper.Token.Composite.Part.Slot→me.bestvibes.exiftoolwrapper.Token.Composite.Partme.bestvibes.exiftoolwrapper.Token.Composite.Part.Text→me.bestvibes.exiftoolwrapper.Token.Composite.Part
- Direction
- Token.Composite.Part uses Token.Composite, so a change to Token.Composite can break Token.Composite.Part, while a change to Token.Composite.Part can't break Token.Composite.
- Position
- Below the diagonal: Token.Composite.Part uses a module listed above it, which is the healthy direction.
18→10 Token.Composite.Part uses me.bestvibes.exiftoolwrapper✕
- Connections
- 1 pair of types, where a type in Token.Composite.Part uses a type in me.bestvibes.exiftoolwrapper.
- The types involved
me.bestvibes.exiftoolwrapper.Token.Composite.Part.Slot→me.bestvibes.exiftoolwrapper.SlotKey
- Direction
- Token.Composite.Part uses me.bestvibes.exiftoolwrapper, so a change to me.bestvibes.exiftoolwrapper can break Token.Composite.Part, while a change to Token.Composite.Part can't break me.bestvibes.exiftoolwrapper.
- Position
- Below the diagonal: Token.Composite.Part 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 | 22 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle; 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 build.gradle. | +6.4 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +8.5 pts | Medium | Security & performance tooling |
| 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. | +5.5 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.6 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.6 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/me/bestvibes/exiftoolwrapper/CommandRunner.kt | 7.2 | Mixed | Cyclomatic Complexity: CommandRunner.run (cyclomatic 24) |
| app/src/main/java/me/bestvibes/exiftoolwrapper/MainActivity.kt | 7.2 | Mixed | Cognitive Complexity: MainActivity.applyActiveCommand (cognitive 17) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/me/bestvibes/exiftoolwrapper/TarReader.kt | 7.4 | Mixed | Cyclomatic Complexity: TarReader.extract (cyclomatic 21) |
| app/src/main/java/me/bestvibes/exiftoolwrapper/CommandParser.kt | 7.8 | Mixed | Cyclomatic Complexity: CommandParser.parse (cyclomatic 36) |
| app/src/main/java/me/bestvibes/exiftoolwrapper/SlotChipSpan.kt | 8.5 | Near-clean | Cognitive Complexity: SlotChipSpanKt.installSlotChipDecoration (cognitive 17) |
| app/build.gradle | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 41 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, 43 of 78 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits for a meaningful bus factor (36 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `app/src/main/java/me/bestvibes/exiftoolwrapper/CommandParser.kt`, `app/src/main/java/me/bestvibes/exiftoolwrapper/TarReader.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits to judge knowledge freshness (36 commit(s) sampled).
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — 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, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin 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.
- IC1 Incompleteness & stubs — 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, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin 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.
- 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CommandParser.parse at 36.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with CommandParser.parse (cyclomatic 36), CommandRunner.run (cyclomatic 24), TarReader.extract (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 3 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was CommandParser.parse at 77.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with CommandParser.parse (cognitive 77), CommandRunner.run (cognitive 43), TarReader.extract (cognitive 34). — 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 3 together lifts Cognitive Complexity from 5.1 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with MainActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with MainActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with MainActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 1.7 % of the production lines (40 of 2,360) are in a reported copy. A further 2 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 copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with CommandRunner.kt, TarReader.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
2 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 88 artifact(s) resolved, 31 of them gradable against Maven Central, and 27 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 4 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 4 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 2360 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 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 build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
3 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
22 finding(s): 0 critical, 22 high, 0 medium, 0 low. 18 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) — `gradlew` (lines 144–145, line 146, line 147, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 18 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 (18 issue-level, 0 of them charged here).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 8 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `./app/src/main/java/me/bestvibes/exiftoolwrapper/CommandSanitizer.kt`, but `app/src/main/java/me/bestvibes/exiftoolwrapper/CommandSanitizer.kt` 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. — README.md:106
What to do
- Reconcile the README with reality: README.md links to `./app/src/main/java/me/bestvibes/exiftoolwrapper/CommandSanitizer.kt`, but `app/src/main/java/me/bestvibes/exiftoolwrapper/CommandSanitizer.kt` does not exist.
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build.gradle:9
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:133
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — app/src/main/java/me/bestvibes/exiftoolwrapper/AssetExtractor.kt:110
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79.9 | Strong | Solid. |
| Architecture | 100.0 | Exemplary | Strongest area. |
| Maturity | 58.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40.5 | Weak — gated by D12, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75.0 | Strong | Solid. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- AXR1 Runtime accessibility (rendered) — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 71 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: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- 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 — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~370 lines of test source are present (.kt) 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.
- D16 Bus Factor — too few commits for a meaningful bus factor
- 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 (383 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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 .kt, 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 — This repository is one build unit, `app` (2360 LoC, 59 module-visible types across 1 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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 included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 22 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — 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
- 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'.
- P2 Observability — This repository's JVM source (1 module(s), 15 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
- X18 Disposal-pattern correctness — 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — 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
- 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 Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) 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.
- 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 — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 17 finding(s)
- Edited copy of a member (10 corresponding lines) app/src/main/java/me/bestvibes/exiftoolwrapper/CommandRunner.kt:248
- Edited copy of a member (10 corresponding lines) app/src/main/java/me/bestvibes/exiftoolwrapper/TarReader.kt:107
- WCAG 2.5.5 reproducibly failed on a screen of the running app
- CommandParser.parse (cyclomatic 36) app/src/main/java/me/bestvibes/exiftoolwrapper/CommandParser.kt:54
- CommandRunner.run (cyclomatic 24) app/src/main/java/me/bestvibes/exiftoolwrapper/CommandRunner.kt:121
- TarReader.extract (cyclomatic 21) app/src/main/java/me/bestvibes/exiftoolwrapper/TarReader.kt:26
- CommandParser.parse (cognitive 77) app/src/main/java/me/bestvibes/exiftoolwrapper/CommandParser.kt:54
- CommandRunner.run (cognitive 43) app/src/main/java/me/bestvibes/exiftoolwrapper/CommandRunner.kt:121
- TarReader.extract (cognitive 34) app/src/main/java/me/bestvibes/exiftoolwrapper/TarReader.kt:26
- CommandRunner.preview (cognitive 30) app/src/main/java/me/bestvibes/exiftoolwrapper/CommandRunner.kt:63
- MainActivity.applyActiveCommand (cognitive 17) app/src/main/java/me/bestvibes/exiftoolwrapper/MainActivity.kt:406
- SlotChipSpanKt.installSlotChipDecoration (cognitive 17) app/src/main/java/me/bestvibes/exiftoolwrapper/SlotChipSpan.kt:109
- ClassTooLong: MainActivity app/src/main/java/me/bestvibes/exiftoolwrapper/MainActivity.kt:47
- TooManyMethods: MainActivity app/src/main/java/me/bestvibes/exiftoolwrapper/MainActivity.kt:47
- FileTooLong: exiftoolwrapper/MainActivity.kt app/src/main/java/me/bestvibes/exiftoolwrapper/MainActivity.kt
- REDACTED
- Swallowed exception (empty catch) app/src/main/java/me/bestvibes/exiftoolwrapper/AssetExtractor.kt:110
Minor — 12 finding(s)
- No ADRs found app/build.gradle:1
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- README/code drift README.md:106
- No SAST
- No dependency-update automation build.gradle:9
- No release approval gate REDACTED:133
- No changelog
- Duplicated predicate app/src/main/java/me/bestvibes/exiftoolwrapper/CommandParser.kt:104
- Silent fallback default in catch app/src/main/java/me/bestvibes/exiftoolwrapper/UserPresets.kt:47
Minor — 27 finding(s)
- Outdated (compile): org.hamcrest:hamcrest-core
- Outdated (compile): com.google.code.findbugs:jsr305
- Outdated (compile): com.google.guava:listenablefuture
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): com.squareup:javawriter
- Outdated (compile): org.hamcrest:hamcrest-library
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-android
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): org.jetbrains.kotlin:kotlin-bom
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): org.jetbrains.kotlinx:atomicfu
- Outdated (compile): org.jetbrains.kotlin:kotlin-build-tools-impl
- Outdated (compile): org.jetbrains.kotlin:kotlin-build-tools-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-compiler-embeddable
- Outdated (compile): org.jetbrains.kotlin:kotlin-script-runtime
- Outdated (compile): org.jetbrains.kotlin:kotlin-reflect
- Outdated (compile): org.jetbrains.kotlin:kotlin-daemon-embeddable
- Outdated (compile): org.jetbrains.kotlin:kotlin-compiler-runner
- Outdated (compile): org.jetbrains.kotlin:kotlin-build-common
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 --report-format json --report-path /tmp/watchdog-gitleaks-74e2e63ace404f6e9c03aec36ea64976/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.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-74e2e63ace404f6e9c03aec36ea64976/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 . | 22 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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. semgrep could not parse 2 file(s) — `app/src/main/java/me/bestvibes/exiftoolwrapper/CommandParser.kt`, `app/src/main/java/me/bestvibes/exiftoolwrapper/TarReader.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |