RepoTrust

Leaderboard github.com

gmegidish/sshdoom

  • View repository ↗
  • C
  • ★ 29
  • commit 36267bee73e2
  • scored 2026-11-13
  • scoring prov-4+qual-2+sec-2

AI provenance

0%

none-detected

Confidence
47%
Coverage
100%

Estimated share of AI-generated code. Explicit attribution is a lower bound.

Code quality

63/100

weak

Confidence
90%
Coverage
100%

Complexity, duplication, lint density, tests, CI, docs and review process.

Security

63/100

weak

Confidence
85%
Coverage
100%

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

  • Repository: https://github.com/gmegidish/sshdoom
  • Commit: 36267bee73e2304d32c7276e43adab28f614d355
  • Generated: 2026-11-13T23:58:22+00:00
  • Scorer 0.1.0, scoring prov-4+qual-2+sec-2, report schema v2

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 0 none-detected 47% 100%
Code quality 63 weak 90% 100%
Security 63 weak 85% 100%

AI provenance

No AI attribution or AI-consistent velocity signals detected.

  • Explicitly attributed share (lower bound): 0.0%

  • Unattributed share in AI-consistent velocity bursts: 0.0%

  • Estimated AI-generated share: 0.0%

  • Stylometry index: 0.50 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 0, emoji 1). Reported as a signal, not scored.

Month Lines added Attributed to AI
2025-08 408 0%

AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.

Code quality

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

Area Score
Complexity (lizard) 66
Duplication 100
Code smells (Opengrep) 100
Tests and CI 15
Documentation 65
Type safety n/a
Process (Scorecard review/maintenance) n/a
  • Functions: 15; mean complexity 4.1, 90th percentile 13; 1 complex and 0 long functions
  • Duplicated lines: 0.0% of 242 compared
  • Tests: 0 test lines for 363 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
  • Docs missing or thin: contributing, changelog

Most complex functions:

Security

Security posture is weak: 1 high-severity SAST findings; 4 high-severity workflow issues. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 100
Static analysis (Opengrep) 53
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) 42
Posture (policy, updates, signing, lockfiles) 20
OpenSSF Scorecard n/a
  • Posture checks passed: signed commits, lockfiles; missing: security policy, dependency updates

Top findings

Severity Finding Location
high opengrep/dockerfile.security.missing-user: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium] Dockerfile:22
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/publish.yml:15
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/publish.yml:20
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/publish.yml:26
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/publish.yml:29
medium zizmor/artipacked: credential persistence through GitHub Actions artifacts [confidence low] .github/workflows/publish.yml:14
medium zizmor/excessive-permissions: overly broad permissions [confidence medium] .github/workflows/publish.yml:10

Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.

Repository profile

  • Source lines: 363; test lines: 0
Language Lines
C 363

Embed a badge

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

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/gmegidish/sshdoom/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/gmegidish/sshdoom/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/gmegidish/sshdoom/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/gmegidish/sshdoom/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/gmegidish/sshdoom/security.svg)](https://repotrust.synapticcyber.com/r/github.com/gmegidish/sshdoom/)