Executive summary
orhun/git-cliff is rated At risk because critical security findings are open. It scores 71 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is fixing the password or key in the code, worth about 3 points. Recording design decisions comes next, worth about 5 points.
Twelve known security holes in the packages the code depends on can be used by attackers. Five secrets can leak from the build pipeline, and three settings leave the servers or containers unsafe. Updating the vulnerable packages, limiting each secret to its own step and correcting the unsafe settings would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions.
The product code is 15,113 lines, about €21,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
New since the last survey: 17 findings
- Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) git-cliff-core/src/release.rs
- Code Duplication · Edited copies of one member (5 members, 27+ corresponding lines) git-cliff-core/src/changelog.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) git-cliff-core/src/template.rs
- Code Duplication · Edited copies of one member (5 members, 30+ corresponding lines) git-cliff-core/src/remote/azure_devops.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) git-cliff-core/src/process.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) git-cliff-core/src/process.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) git-cliff/src/logger.rs
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) git-cliff-core/src/remote/bitbucket.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 6 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2026-0381 REDACTED
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2026-0382 REDACTED
- Documentation (README) · README may be stale
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €6,900 to €35,000, for 115 to 366 hours of work, about 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 | ×1.0 at a score of 71. 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: 15,113 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 git_cliff.bin.completions | 2 git_cliff.bin.mangen | 3 git_cliff.config_path | 4 git_cliff.file | 5 git_cliff.logger | 6 git_cliff.main | 7 git_cliff.profiler | 8 git_cliff_core.command | 9 git_cliff_core.config | 10 git_cliff_core.config.serde_pattern | 11 git_cliff_core.contributor | 12 git_cliff_core.embed.inner | 13 git_cliff_core.error | 14 git_cliff_core.markdown | 15 git_cliff_core.summary | 16 git_cliff_core.tag | 17 git_cliff_core.template | 18 npm.git-cliff | 19 npm.git-cliff.src | 20 website.src | 21 website.src.components | 22 git_cliff.args | 23 git_cliff_core.commit | 24 git_cliff_core.remote | 25 git_cliff_core.statistics | 26 git_cliff_core.process | 27 git_cliff_core.release | 28 git_cliff_core.remote.azure_devops | 29 git_cliff_core.remote.bitbucket | 30 git_cliff_core.remote.gitlab | 31 git_cliff_core.repo | 32 git_cliff_core.changelog | 33 git_cliff_core.remote.gitea | 34 git_cliff_core.remote.github | 35 git_cliff |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 git_cliff.bin.completions | |||||||||||||||||||||||||||||||||||
| 2 git_cliff.bin.mangen | |||||||||||||||||||||||||||||||||||
| 3 git_cliff.config_path | |||||||||||||||||||||||||||||||||||
| 4 git_cliff.file | |||||||||||||||||||||||||||||||||||
| 5 git_cliff.logger | |||||||||||||||||||||||||||||||||||
| 6 git_cliff.main | |||||||||||||||||||||||||||||||||||
| 7 git_cliff.profiler | |||||||||||||||||||||||||||||||||||
| 8 git_cliff_core.command | |||||||||||||||||||||||||||||||||||
| 9 git_cliff_core.config | |||||||||||||||||||||||||||||||||||
| 10 git_cliff_core.config.serde_pattern | |||||||||||||||||||||||||||||||||||
| 11 git_cliff_core.contributor | |||||||||||||||||||||||||||||||||||
| 12 git_cliff_core.embed.inner | |||||||||||||||||||||||||||||||||||
| 13 git_cliff_core.error | |||||||||||||||||||||||||||||||||||
| 14 git_cliff_core.markdown | |||||||||||||||||||||||||||||||||||
| 15 git_cliff_core.summary | |||||||||||||||||||||||||||||||||||
| 16 git_cliff_core.tag | |||||||||||||||||||||||||||||||||||
| 17 git_cliff_core.template | |||||||||||||||||||||||||||||||||||
| 18 npm.git-cliff | |||||||||||||||||||||||||||||||||||
| 19 npm.git-cliff.src | |||||||||||||||||||||||||||||||||||
| 20 website.src | |||||||||||||||||||||||||||||||||||
| 21 website.src.components | |||||||||||||||||||||||||||||||||||
| 22 git_cliff.args | 1 | ||||||||||||||||||||||||||||||||||
| 23 git_cliff_core.commit | 2 | 1 | |||||||||||||||||||||||||||||||||
| 24 git_cliff_core.remote | 1 | 1 | |||||||||||||||||||||||||||||||||
| 25 git_cliff_core.statistics | 1 | ||||||||||||||||||||||||||||||||||
| 26 git_cliff_core.process | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 27 git_cliff_core.release | 4 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 28 git_cliff_core.remote.azure_devops | 1 | 3 | |||||||||||||||||||||||||||||||||
| 29 git_cliff_core.remote.bitbucket | 1 | 3 | |||||||||||||||||||||||||||||||||
| 30 git_cliff_core.remote.gitlab | 1 | 3 | |||||||||||||||||||||||||||||||||
| 31 git_cliff_core.repo | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 git_cliff_core.changelog | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 git_cliff_core.remote.gitea | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 34 git_cliff_core.remote.github | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 35 git_cliff | 1 | 1 | 1 | 1 | 1 |
22→9 git_cliff.args uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff.args uses a type in git_cliff_core.config.
- The types involved
git_cliff.args.RemoteValue→git_cliff_core.config.Remote
- Direction
- git_cliff.args uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff.args, while a change to git_cliff.args can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff.args uses a module listed above it, which is the healthy direction.
23→9 git_cliff_core.commit uses git_cliff_core.config✕
- Connections
- 2 pairs of types, where a type in git_cliff_core.commit uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.commit.Commit→git_cliff_core.config.CommitParsergit_cliff_core.commit.Commit→git_cliff_core.config.GitConfig
- Direction
- git_cliff_core.commit uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.commit, while a change to git_cliff_core.commit can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.commit uses a module listed above it, which is the healthy direction.
23→11 git_cliff_core.commit uses git_cliff_core.contributor✕
- Connections
- 1 pair of types, where a type in git_cliff_core.commit uses a type in git_cliff_core.contributor.
- The types involved
git_cliff_core.commit.Commit→git_cliff_core.contributor.RemoteContributor
- Direction
- git_cliff_core.commit uses git_cliff_core.contributor, so a change to git_cliff_core.contributor can break git_cliff_core.commit, while a change to git_cliff_core.commit can't break git_cliff_core.contributor.
- Position
- Below the diagonal: git_cliff_core.commit uses a module listed above it, which is the healthy direction.
24→9 git_cliff_core.remote uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.remote.RemoteClient→git_cliff_core.config.Remote
- Direction
- git_cliff_core.remote uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.remote, while a change to git_cliff_core.remote can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.remote uses a module listed above it, which is the healthy direction.
24→11 git_cliff_core.remote uses git_cliff_core.contributor✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote uses a type in git_cliff_core.contributor.
- The types involved
git_cliff_core.remote.RemoteReleaseMetadata→git_cliff_core.contributor.RemoteContributor
- Direction
- git_cliff_core.remote uses git_cliff_core.contributor, so a change to git_cliff_core.contributor can break git_cliff_core.remote, while a change to git_cliff_core.remote can't break git_cliff_core.contributor.
- Position
- Below the diagonal: git_cliff_core.remote uses a module listed above it, which is the healthy direction.
25→27 git_cliff_core.statistics uses git_cliff_core.release part of a loop✕
- Connections
- 1 pair of types, where a type in git_cliff_core.statistics uses a type in git_cliff_core.release.
- The types involved
git_cliff_core.statistics.Statistics→git_cliff_core.release.Release
- Direction
- git_cliff_core.statistics uses git_cliff_core.release, so a change to git_cliff_core.release can break git_cliff_core.statistics, while a change to git_cliff_core.statistics can't break git_cliff_core.release.
- 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.
26→9 git_cliff_core.process uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.process uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.process.CommitProcessor→git_cliff_core.config.GitConfig
- Direction
- git_cliff_core.process uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.process, while a change to git_cliff_core.process can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.process uses a module listed above it, which is the healthy direction.
26→15 git_cliff_core.process uses git_cliff_core.summary✕
- Connections
- 1 pair of types, where a type in git_cliff_core.process uses a type in git_cliff_core.summary.
- The types involved
git_cliff_core.process.CommitProcessor→git_cliff_core.summary.Summary
- Direction
- git_cliff_core.process uses git_cliff_core.summary, so a change to git_cliff_core.summary can break git_cliff_core.process, while a change to git_cliff_core.process can't break git_cliff_core.summary.
- Position
- Below the diagonal: git_cliff_core.process uses a module listed above it, which is the healthy direction.
26→23 git_cliff_core.process uses git_cliff_core.commit✕
- Connections
- 1 pair of types, where a type in git_cliff_core.process uses a type in git_cliff_core.commit.
- The types involved
git_cliff_core.process.CommitProcessor→git_cliff_core.commit.Commit
- Direction
- git_cliff_core.process uses git_cliff_core.commit, so a change to git_cliff_core.commit can break git_cliff_core.process, while a change to git_cliff_core.process can't break git_cliff_core.commit.
- Position
- Below the diagonal: git_cliff_core.process uses a module listed above it, which is the healthy direction.
27→9 git_cliff_core.release uses git_cliff_core.config✕
- Connections
- 4 pairs of types, where a type in git_cliff_core.release uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.release.NextVersion→git_cliff_core.config.BumpTypegit_cliff_core.release.Release→git_cliff_core.config.Bumpgit_cliff_core.release.Release→git_cliff_core.config.BumpTypegit_cliff_core.release.release$module→git_cliff_core.config.BumpType
- Direction
- git_cliff_core.release uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.release, while a change to git_cliff_core.release can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.release uses a module listed above it, which is the healthy direction.
27→23 git_cliff_core.release uses git_cliff_core.commit✕
- Connections
- 2 pairs of types, where a type in git_cliff_core.release uses a type in git_cliff_core.commit.
- The types involved
git_cliff_core.release.Release→git_cliff_core.commit.Commitgit_cliff_core.release.Release→git_cliff_core.commit.Range
- Direction
- git_cliff_core.release uses git_cliff_core.commit, so a change to git_cliff_core.commit can break git_cliff_core.release, while a change to git_cliff_core.release can't break git_cliff_core.commit.
- Position
- Below the diagonal: git_cliff_core.release uses a module listed above it, which is the healthy direction.
27→24 git_cliff_core.release uses git_cliff_core.remote✕
- Connections
- 1 pair of types, where a type in git_cliff_core.release uses a type in git_cliff_core.remote.
- The types involved
git_cliff_core.release.Release→git_cliff_core.remote.RemoteReleaseMetadata
- Direction
- git_cliff_core.release uses git_cliff_core.remote, so a change to git_cliff_core.remote can break git_cliff_core.release, while a change to git_cliff_core.release can't break git_cliff_core.remote.
- Position
- Below the diagonal: git_cliff_core.release uses a module listed above it, which is the healthy direction.
27→25 git_cliff_core.release uses git_cliff_core.statistics✕
- Connections
- 1 pair of types, where a type in git_cliff_core.release uses a type in git_cliff_core.statistics.
- The types involved
git_cliff_core.release.Release→git_cliff_core.statistics.Statistics
- Direction
- git_cliff_core.release uses git_cliff_core.statistics, so a change to git_cliff_core.statistics can break git_cliff_core.release, while a change to git_cliff_core.release can't break git_cliff_core.statistics.
- Position
- Below the diagonal: git_cliff_core.release uses a module listed above it, which is the healthy direction.
28→9 git_cliff_core.remote.azure_devops uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.azure_devops uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.remote.azure_devops.AzureDevOpsClient→git_cliff_core.config.Remote
- Direction
- git_cliff_core.remote.azure_devops uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.remote.azure_devops, while a change to git_cliff_core.remote.azure_devops can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.remote.azure_devops uses a module listed above it, which is the healthy direction.
28→24 git_cliff_core.remote.azure_devops uses git_cliff_core.remote✕
- Connections
- 3 pairs of types, where a type in git_cliff_core.remote.azure_devops uses a type in git_cliff_core.remote.
- The types involved
git_cliff_core.remote.azure_devops.AzureDevOpsClient→git_cliff_core.remote.RemoteClientgit_cliff_core.remote.azure_devops.AzureDevOpsCommit→git_cliff_core.remote.RemoteCommitgit_cliff_core.remote.azure_devops.AzureDevOpsPullRequest→git_cliff_core.remote.RemotePullRequest
- Direction
- git_cliff_core.remote.azure_devops uses git_cliff_core.remote, so a change to git_cliff_core.remote can break git_cliff_core.remote.azure_devops, while a change to git_cliff_core.remote.azure_devops can't break git_cliff_core.remote.
- Position
- Below the diagonal: git_cliff_core.remote.azure_devops uses a module listed above it, which is the healthy direction.
29→9 git_cliff_core.remote.bitbucket uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.bitbucket uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.remote.bitbucket.BitbucketClient→git_cliff_core.config.Remote
- Direction
- git_cliff_core.remote.bitbucket uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.remote.bitbucket, while a change to git_cliff_core.remote.bitbucket can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.remote.bitbucket uses a module listed above it, which is the healthy direction.
29→24 git_cliff_core.remote.bitbucket uses git_cliff_core.remote✕
- Connections
- 3 pairs of types, where a type in git_cliff_core.remote.bitbucket uses a type in git_cliff_core.remote.
- The types involved
git_cliff_core.remote.bitbucket.BitbucketClient→git_cliff_core.remote.RemoteClientgit_cliff_core.remote.bitbucket.BitbucketCommit→git_cliff_core.remote.RemoteCommitgit_cliff_core.remote.bitbucket.BitbucketPullRequest→git_cliff_core.remote.RemotePullRequest
- Direction
- git_cliff_core.remote.bitbucket uses git_cliff_core.remote, so a change to git_cliff_core.remote can break git_cliff_core.remote.bitbucket, while a change to git_cliff_core.remote.bitbucket can't break git_cliff_core.remote.
- Position
- Below the diagonal: git_cliff_core.remote.bitbucket uses a module listed above it, which is the healthy direction.
30→9 git_cliff_core.remote.gitlab uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.gitlab uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.remote.gitlab.GitLabClient→git_cliff_core.config.Remote
- Direction
- git_cliff_core.remote.gitlab uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.remote.gitlab, while a change to git_cliff_core.remote.gitlab can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.remote.gitlab uses a module listed above it, which is the healthy direction.
30→24 git_cliff_core.remote.gitlab uses git_cliff_core.remote✕
- Connections
- 3 pairs of types, where a type in git_cliff_core.remote.gitlab uses a type in git_cliff_core.remote.
- The types involved
git_cliff_core.remote.gitlab.GitLabClient→git_cliff_core.remote.RemoteClientgit_cliff_core.remote.gitlab.GitLabCommit→git_cliff_core.remote.RemoteCommitgit_cliff_core.remote.gitlab.GitLabMergeRequest→git_cliff_core.remote.RemotePullRequest
- Direction
- git_cliff_core.remote.gitlab uses git_cliff_core.remote, so a change to git_cliff_core.remote can break git_cliff_core.remote.gitlab, while a change to git_cliff_core.remote.gitlab can't break git_cliff_core.remote.
- Position
- Below the diagonal: git_cliff_core.remote.gitlab uses a module listed above it, which is the healthy direction.
31→16 git_cliff_core.repo uses git_cliff_core.tag✕
- Connections
- 1 pair of types, where a type in git_cliff_core.repo uses a type in git_cliff_core.tag.
- The types involved
git_cliff_core.repo.Repository→git_cliff_core.tag.Tag
- Direction
- git_cliff_core.repo uses git_cliff_core.tag, so a change to git_cliff_core.tag can break git_cliff_core.repo, while a change to git_cliff_core.repo can't break git_cliff_core.tag.
- Position
- Below the diagonal: git_cliff_core.repo uses a module listed above it, which is the healthy direction.
31→23 git_cliff_core.repo uses git_cliff_core.commit✕
- Connections
- 1 pair of types, where a type in git_cliff_core.repo uses a type in git_cliff_core.commit.
- The types involved
git_cliff_core.repo.Repository→git_cliff_core.commit.Commit
- Direction
- git_cliff_core.repo uses git_cliff_core.commit, so a change to git_cliff_core.commit can break git_cliff_core.repo, while a change to git_cliff_core.repo can't break git_cliff_core.commit.
- Position
- Below the diagonal: git_cliff_core.repo uses a module listed above it, which is the healthy direction.
32→9 git_cliff_core.changelog uses git_cliff_core.config✕
- Connections
- 2 pairs of types, where a type in git_cliff_core.changelog uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.changelog.Changelog→git_cliff_core.config.Configgit_cliff_core.changelog.changelog$module→git_cliff_core.config.Config
- Direction
- git_cliff_core.changelog uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.changelog, while a change to git_cliff_core.changelog can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.changelog uses a module listed above it, which is the healthy direction.
32→17 git_cliff_core.changelog uses git_cliff_core.template✕
- Connections
- 1 pair of types, where a type in git_cliff_core.changelog uses a type in git_cliff_core.template.
- The types involved
git_cliff_core.changelog.Changelog→git_cliff_core.template.Template
- Direction
- git_cliff_core.changelog uses git_cliff_core.template, so a change to git_cliff_core.template can break git_cliff_core.changelog, while a change to git_cliff_core.changelog can't break git_cliff_core.template.
- Position
- Below the diagonal: git_cliff_core.changelog uses a module listed above it, which is the healthy direction.
32→27 git_cliff_core.changelog uses git_cliff_core.release✕
- Connections
- 1 pair of types, where a type in git_cliff_core.changelog uses a type in git_cliff_core.release.
- The types involved
git_cliff_core.changelog.Changelog→git_cliff_core.release.Release
- Direction
- git_cliff_core.changelog uses git_cliff_core.release, so a change to git_cliff_core.release can break git_cliff_core.changelog, while a change to git_cliff_core.changelog can't break git_cliff_core.release.
- Position
- Below the diagonal: git_cliff_core.changelog uses a module listed above it, which is the healthy direction.
33→9 git_cliff_core.remote.gitea uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.gitea uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.remote.gitea.GiteaClient→git_cliff_core.config.Remote
- Direction
- git_cliff_core.remote.gitea uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.remote.gitea, while a change to git_cliff_core.remote.gitea can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.remote.gitea uses a module listed above it, which is the healthy direction.
33→24 git_cliff_core.remote.gitea uses git_cliff_core.remote✕
- Connections
- 3 pairs of types, where a type in git_cliff_core.remote.gitea uses a type in git_cliff_core.remote.
- The types involved
git_cliff_core.remote.gitea.GiteaClient→git_cliff_core.remote.RemoteClientgit_cliff_core.remote.gitea.GiteaCommit→git_cliff_core.remote.RemoteCommitgit_cliff_core.remote.gitea.GiteaPullRequest→git_cliff_core.remote.RemotePullRequest
- Direction
- git_cliff_core.remote.gitea uses git_cliff_core.remote, so a change to git_cliff_core.remote can break git_cliff_core.remote.gitea, while a change to git_cliff_core.remote.gitea can't break git_cliff_core.remote.
- Position
- Below the diagonal: git_cliff_core.remote.gitea uses a module listed above it, which is the healthy direction.
33→29 git_cliff_core.remote.gitea uses git_cliff_core.remote.bitbucket✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.gitea uses a type in git_cliff_core.remote.bitbucket.
- The types involved
git_cliff_core.remote.gitea.GiteaPullRequest→git_cliff_core.remote.bitbucket.PullRequestLabel
- Direction
- git_cliff_core.remote.gitea uses git_cliff_core.remote.bitbucket, so a change to git_cliff_core.remote.bitbucket can break git_cliff_core.remote.gitea, while a change to git_cliff_core.remote.gitea can't break git_cliff_core.remote.bitbucket.
- Position
- Below the diagonal: git_cliff_core.remote.gitea uses a module listed above it, which is the healthy direction.
34→9 git_cliff_core.remote.github uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.github uses a type in git_cliff_core.config.
- The types involved
git_cliff_core.remote.github.GitHubClient→git_cliff_core.config.Remote
- Direction
- git_cliff_core.remote.github uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff_core.remote.github, while a change to git_cliff_core.remote.github can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff_core.remote.github uses a module listed above it, which is the healthy direction.
34→24 git_cliff_core.remote.github uses git_cliff_core.remote✕
- Connections
- 3 pairs of types, where a type in git_cliff_core.remote.github uses a type in git_cliff_core.remote.
- The types involved
git_cliff_core.remote.github.GitHubClient→git_cliff_core.remote.RemoteClientgit_cliff_core.remote.github.GitHubCommit→git_cliff_core.remote.RemoteCommitgit_cliff_core.remote.github.GitHubPullRequest→git_cliff_core.remote.RemotePullRequest
- Direction
- git_cliff_core.remote.github uses git_cliff_core.remote, so a change to git_cliff_core.remote can break git_cliff_core.remote.github, while a change to git_cliff_core.remote.github can't break git_cliff_core.remote.
- Position
- Below the diagonal: git_cliff_core.remote.github uses a module listed above it, which is the healthy direction.
34→29 git_cliff_core.remote.github uses git_cliff_core.remote.bitbucket✕
- Connections
- 1 pair of types, where a type in git_cliff_core.remote.github uses a type in git_cliff_core.remote.bitbucket.
- The types involved
git_cliff_core.remote.github.GitHubPullRequest→git_cliff_core.remote.bitbucket.PullRequestLabel
- Direction
- git_cliff_core.remote.github uses git_cliff_core.remote.bitbucket, so a change to git_cliff_core.remote.bitbucket can break git_cliff_core.remote.github, while a change to git_cliff_core.remote.github can't break git_cliff_core.remote.bitbucket.
- Position
- Below the diagonal: git_cliff_core.remote.github uses a module listed above it, which is the healthy direction.
35→9 git_cliff uses git_cliff_core.config✕
- Connections
- 1 pair of types, where a type in git_cliff uses a type in git_cliff_core.config.
- The types involved
git_cliff.git_cliff$module→git_cliff_core.config.Config
- Direction
- git_cliff uses git_cliff_core.config, so a change to git_cliff_core.config can break git_cliff, while a change to git_cliff can't break git_cliff_core.config.
- Position
- Below the diagonal: git_cliff uses a module listed above it, which is the healthy direction.
35→22 git_cliff uses git_cliff.args✕
- Connections
- 1 pair of types, where a type in git_cliff uses a type in git_cliff.args.
- The types involved
git_cliff.git_cliff$module→git_cliff.args.Opt
- Direction
- git_cliff uses git_cliff.args, so a change to git_cliff.args can break git_cliff, while a change to git_cliff can't break git_cliff.args.
- Position
- Below the diagonal: git_cliff uses a module listed above it, which is the healthy direction.
35→27 git_cliff uses git_cliff_core.release✕
- Connections
- 1 pair of types, where a type in git_cliff uses a type in git_cliff_core.release.
- The types involved
git_cliff.git_cliff$module→git_cliff_core.release.Release
- Direction
- git_cliff uses git_cliff_core.release, so a change to git_cliff_core.release can break git_cliff, while a change to git_cliff can't break git_cliff_core.release.
- Position
- Below the diagonal: git_cliff uses a module listed above it, which is the healthy direction.
35→31 git_cliff uses git_cliff_core.repo✕
- Connections
- 1 pair of types, where a type in git_cliff uses a type in git_cliff_core.repo.
- The types involved
git_cliff.git_cliff$module→git_cliff_core.repo.Repository
- Direction
- git_cliff uses git_cliff_core.repo, so a change to git_cliff_core.repo can break git_cliff, while a change to git_cliff can't break git_cliff_core.repo.
- Position
- Below the diagonal: git_cliff uses a module listed above it, which is the healthy direction.
35→32 git_cliff uses git_cliff_core.changelog✕
- Connections
- 1 pair of types, where a type in git_cliff uses a type in git_cliff_core.changelog.
- The types involved
git_cliff.git_cliff$module→git_cliff_core.changelog.Changelog
- Direction
- git_cliff uses git_cliff_core.changelog, so a change to git_cliff_core.changelog can break git_cliff, while a change to git_cliff can't break git_cliff_core.changelog.
- Position
- Below the diagonal: git_cliff 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 — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 56 | High / Critical |
| A05:2025 — Injection | 24 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
Roadmap
Top priorities: 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 build/run (quick start) section to the root README — the first thing a newcomer needs; Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +2.5 pts | Low | REDACTED Scanning |
| 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. | +4.6 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.9 pts | Medium | Documentation (README) |
| Interpolated log message defeats structured logging | +2.3 pts | Medium | Structured logging |
| Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs, commit.rs. | +0.8 pts | Medium | Churn × Complexity Hotspots |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.6 pts | Low | Bus Factor |
| Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with Commit::parse (cognitive 100), git_cliff::process_repository (cognitive 75), git_cliff::run_with_changelog_modifier (cognitive 71). | +1.1 pts | High | Cognitive Complexity |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.1 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.5 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| git-cliff/src/lib.rs | 7.0 | Near-clean | Cyclomatic Complexity: git_cliff::run_with_changelog_modifier (cyclomatic 54) |
| git-cliff-core/src/release.rs | 7.0 | Near-clean | Cyclomatic Complexity: Release::calculate_next_version_from_commits (cyclomatic 18) |
| git-cliff-core/src/changelog.rs | 7.1 | Near-clean | Cognitive Complexity: Changelog::add_remote_data (cognitive 19) |
| git-cliff-core/src/template.rs | 7.2 | Near-clean | Cyclomatic Complexity: Template::find_identifiers (cyclomatic 21) |
| git-cliff-core/src/process.rs | 7.2 | Near-clean | Cognitive Complexity: CommitProcessor::run_legacy (cognitive 21) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| git-cliff-core/src/commit.rs | 7.4 | Near-clean | Cyclomatic Complexity: Commit::parse (cyclomatic 38) |
| git-cliff-core/src/remote/azure_devops.rs | 7.4 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| git-cliff/src/args.rs | 7.8 | Near-clean | God Classes: TooManyFields: Opt |
| git-cliff-core/src/remote/gitea.rs | 7.8 | Near-clean | Code Duplication: Duplicated block (24 lines × 3) |
| REDACTED | 7.9 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
| REDACTED | 7.9 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
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 56 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 — 56 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, 171 of 195 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 JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — website/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a Codecov configuration (codecov.yml) and a coverage step in CI (`cargo tarpaulin`) shows coverage is measured in your own CI.
- D10 Test 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. The 1 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 2 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D14 License Compliance — 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. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 on C# first (docs/plans/deterministic-engine.md, P5): 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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.
- 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. `npm/git-cliff/tsup.config.ts` 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.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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 and Scala source only, and this repository's Rust is most of its product and 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 and Scala source only, and this repository's Rust is most of its product and 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.
- 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.
- X12 Unreachable branch — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — 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. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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 REDACTED Scanning: REDACTED 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- 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.
- 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 REDACTED (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.
- 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.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was git_cliff::run_with_changelog_modifier at 54.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with git_cliff::run_with_changelog_modifier (cyclomatic 54), git_cliff::process_repository (cyclomatic 48), Commit::parse (cyclomatic 38). — 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 7 together lifts Cyclomatic Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was Commit::parse at 100.
What to do
- Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with Commit::parse (cognitive 100), git_cliff::process_repository (cognitive 75), git_cliff::run_with_changelog_modifier (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 6 together lifts Cognitive Complexity from 4.3 to about 7.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with lib.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with lib.rs, changelog.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyFields finding(s) in God Classes — start with args.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 3.7 % of the production lines (555 of 15,113) are in a reported copy. A further 9 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 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with process.rs, args.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with changelog.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with azure_devops.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 14 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests. Measured on the JavaScript/TypeScript suite only — at least 2 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 24 test files): measured (0 flaky).
D12 · Dependency Hygiene
14 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 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 429 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: git-cliff/src/lib.rs (12×54=648); git-cliff-core/src/commit.rs (6×38=228)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs, commit.rs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is git-cliff/src/config_path.rs. Counted over 27 of the 34 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 15113 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. 54 document(s) read across 3 unit(s).
D26 · Project Cohesion
0 of 4 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
24 finding(s): 0 critical, 10 high, 14 medium, 0 low. semgrep hit a parse error in 1 file(s) — `npm/git-cliff/tsup.config.ts` (line 2) — 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 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- 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).
D30 · Dependency Vulnerabilities
47 finding(s): 1 critical, 11 high, 34 medium, 1 low.
What to do
- Resolve the 16 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (16). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED. — One of this dimension's main actionable groups (11 issue-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
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
1 of 27 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is npm/git-cliff/src/options.ts. Counted over 27 of the 34 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
Build pipeline generates provenance, signs artifacts and produces an SBOM.
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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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 0 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
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `npm/git-cliff`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, 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:2
What to do
- Dependabot is configured but does not watch `pip` — 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
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R6 · Tooling
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 130 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:130
- `warn!` at line 142 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:142
- `debug!` at line 144 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — git-cliff-core/src/changelog.rs:144, git-cliff/src/lib.rs:144
- `debug!` at line 198 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:198
- `debug!` at line 211 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:211
- `debug!` at line 216 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:216
- `debug!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:282
- `debug!` at line 283 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:283
- `error!` at line 327 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:327
- `debug!` at line 341 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:341
- `debug!` at line 342 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:342
- `debug!` at line 384 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:384
- `debug!` at line 385 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:385
- `debug!` at line 432 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:432
- `debug!` at line 433 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:433
- `debug!` at line 479 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:479
- `debug!` at line 480 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:480
- `debug!` at line 612 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:612
- `warn!` at line 771 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:771
- `warn!` at line 816 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/changelog.rs:816
- `trace!` at line 12 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/command.rs:12
- `error!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/command.rs:48
- `trace!` at line 381 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/commit.rs:381
- `trace!` at line 408 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/commit.rs:408
- `warn!` at line 463 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/config.rs:463
- `debug!` at line 603 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/config.rs:603
- `error!` at line 205 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/process.rs:205
- `error!` at line 232 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/process.rs:232
- `trace!` at line 256 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/process.rs:256
- `trace!` at line 306 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/repo.rs:306
- `error!` at line 433 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/repo.rs:433
- `error!` at line 440 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/repo.rs:440
- `trace!` at line 691 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/repo.rs:691
- `trace!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/statistics.rs:58
- `trace!` at line 308 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/template.rs:308
- `debug!` at line 174 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/remote/mod.rs:174
- `trace!` at line 178 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/remote/mod.rs:178
- `error!` at line 182 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff-core/src/remote/mod.rs:182
- `info!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-cliff/src/lib.rs:44
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71% | Strong | Solid. |
| Security | 81% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | 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 — 78 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; this repository's TypeScript 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 — 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 exported interface declares behaviour
- 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 — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: 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.
- 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.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (971 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# 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; comments in this repository's .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- 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 — JavaScript/TypeScript suite
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, 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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (4 production file(s)) has no JavaScript/TypeScript test, but it is 3.24% of this repository's production source and the other 96.76% carries 347 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — No web surface: 31 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 3% of this repository's production lines — rust (14,649 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X16 Unfloored truncation loop — 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 — 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 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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: 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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. 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 — X3 reached only 3% of this repository's production lines — rust (14,649 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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.
- 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 — 27 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
Serious — 104 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Release::calculate_next_version_from_commits (cognitive 36) git-cliff-core/src/release.rs:142
- Release::update_github_metadata (cognitive 16) git-cliff-core/src/release.rs:72
- Release::update_gitlab_metadata (cognitive 16) git-cliff-core/src/release.rs:75
- Release::update_gitea_metadata (cognitive 16) git-cliff-core/src/release.rs:78
- Release::update_bitbucket_metadata (cognitive 16) git-cliff-core/src/release.rs:81
- Release::update_azure_devops_metadata (cognitive 16) git-cliff-core/src/release.rs:84
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- git_cliff::run_with_changelog_modifier (cyclomatic 54) git-cliff/src/lib.rs:631
- git_cliff::process_repository (cyclomatic 48) git-cliff/src/lib.rs:237
- git_cliff::write_changelog (cyclomatic 18) git-cliff/src/lib.rs:929
- git_cliff::determine_commit_range (cyclomatic 16) git-cliff/src/lib.rs:52
- git_cliff::process_repository (cognitive 75) git-cliff/src/lib.rs:237
- git_cliff::run_with_changelog_modifier (cognitive 71) git-cliff/src/lib.rs:631
- git_cliff::determine_commit_range (cognitive 40) git-cliff/src/lib.rs:52
- git_cliff::write_changelog (cognitive 27) git-cliff/src/lib.rs:929
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: git-cliff/src/lib.rs git-cliff/src/lib.rs:631
- Hotspot: git-cliff-core/src/commit.rs git-cliff-core/src/commit.rs:322
- FunctionTooLong: git_cliff::process_repository git-cliff/src/lib.rs:237
- FunctionTooLong: git_cliff::run_with_changelog_modifier git-cliff/src/lib.rs:631
- FileTooLong: src/lib.rs git-cliff/src/lib.rs
- FileTooLong: src/changelog.rs git-cliff-core/src/changelog.rs
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) git-cliff-core/src/process.rs:207
- Duplicated block (11 lines × 2) git-cliff/src/args.rs:443
- Duplicated block (8 lines × 2) git-cliff-core/src/changelog.rs:274
- Duplicated block (8 lines × 2) git-cliff-core/src/changelog.rs:424
- Commit::parse (cyclomatic 38) git-cliff-core/src/commit.rs:322
- Template::find_identifiers (cyclomatic 21) git-cliff-core/src/template.rs:244
- Release::calculate_next_version_from_commits (cyclomatic 18) git-cliff-core/src/release.rs:142
- Commit::parse (cognitive 100) git-cliff-core/src/commit.rs:322
- Template::find_identifiers (cognitive 33) git-cliff-core/src/template.rs:244
- CommitProcessor::run_legacy (cognitive 21) git-cliff-core/src/process.rs:51
- Changelog::add_remote_data (cognitive 19) git-cliff-core/src/changelog.rs:503
- Repository::tags (cognitive 17) git-cliff-core/src/repo.rs:558
- TooManyFields: Opt git-cliff/src/args.rs:54
- MethodTooLong: Commit.parse git-cliff-core/src/commit.rs:322
- ClassTooLong: Changelog git-cliff-core/src/changelog.rs:24
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) git-cliff-core/src/remote/azure_devops.rs:246
- Edited copies of one member (5 members, 1+ corresponding lines) git-cliff-core/src/release.rs:72
- Edited copies of one member (5 members, 27+ corresponding lines) git-cliff-core/src/changelog.rs:263
- Edited copy of a member (21 corresponding lines) git-cliff-core/src/template.rs:161
- Edited copies of one member (5 members, 30+ corresponding lines) git-cliff-core/src/remote/azure_devops.rs:283
- Edited copy of a member (24 corresponding lines) git-cliff-core/src/process.rs:200
- Edited copy of a member (16 corresponding lines) git-cliff-core/src/process.rs:76
- Edited copy of a member (9 corresponding lines) git-cliff/src/logger.rs:83
- Edited copies of one member (3 members, 12+ corresponding lines) git-cliff-core/src/remote/bitbucket.rs:159
- Duplicated block (24 lines × 3) git-cliff-core/src/remote/gitea.rs:179
- Duplicated block (24 lines × 2) git-cliff-core/src/remote/gitea.rs:212
- Duplicated block (7–8 lines × 4) git-cliff-core/src/remote/azure_devops.rs:247
- Duplicated block (9 lines × 2) git-cliff-core/src/template.rs:167
- Off the main sequence: git-cliff-core
Minor — 50 finding(s)
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:130
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:142
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:144
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:198
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:211
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:216
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:282
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:283
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:327
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:341
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:342
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:384
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:385
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:432
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:433
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:479
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:480
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:612
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:771
- Interpolated log message defeats structured logging git-cliff-core/src/changelog.rs:816
- Interpolated log message defeats structured logging git-cliff-core/src/command.rs:12
- Interpolated log message defeats structured logging git-cliff-core/src/command.rs:48
- Interpolated log message defeats structured logging git-cliff-core/src/commit.rs:381
- Interpolated log message defeats structured logging git-cliff-core/src/commit.rs:408
- Interpolated log message defeats structured logging git-cliff-core/src/config.rs:463
- Off-boarding risk: anonymized user #1
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file npm/git-cliff/src/options.ts:1
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- Dependabot does not watch pip REDACTED:2
Minor — 14 finding(s)
- Outdated: clap
- Outdated: clap_complete
- Outdated: config
- Outdated: glob
- Outdated: indexmap
- Outdated: next_version
- Outdated: owo-colors
- Outdated: pulldown-cmark
- Outdated: regex
- Outdated: rust-embed
- Outdated: serde_json
- Outdated: thiserror
- Outdated: tokio
- Outdated: url
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-cca8095a18f145aabc36319194877bd2/history.json --exit-code 0 --source . | 7 | 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-cca8095a18f145aabc36319194877bd2/tree.json --exit-code 0 --source . | 4 | 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 . | 24 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 47 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | 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. semgrep could not parse 1 file(s) — `npm/git-cliff/tsup.config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |