gomatcha/matcha
Build native mobile apps in Go.
- Repository: https://github.com/gomatcha/matcha
- Commit:
d2dd1c5db1f5c1a7c0de70ead920a999e1e2bc9a - Generated: 2026-11-13T23:40:26+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 | 65% | 100% |
| Code quality | 43 | poor | 78% | 83% |
| Security | 81 | adequate | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
- Explicitly attributed share (lower bound): 0.0%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 0.0%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2017-08 | 158,984 | 0% |
| 2017-09 | 39,252 | 0% |
| 2017-10 | 10,538 | 0% |
| 2017-11 | 308 | 0% |
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is poor: test-to-source ratio 0.01, no CI test run detected; 32% duplicated lines. Weakest area: duplication.
| Area | Score |
|---|---|
| Complexity (lizard) | n/a |
| Duplication | 14 |
| Code smells (Opengrep) | 92 |
| Tests and CI | 22 |
| Documentation | 65 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Duplicated lines: 32.4% of 76,638 compared
- Tests: 666 test lines for 104,990 source lines (ratio 0.01); CI test commands: none detected; 4% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 99 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| medium | opengrep/go.lang.security.audit.unsafe-reflect-by-name: If an attacker can supply values that the application then uses to determine which method or field to invoke, the potential exists for the attacker to create control flow paths through the application that were not intended by the application developers. This attack vector may allow the attacker to [confidence low] |
bridge/go-go.go:198 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
bridge/java-foreign.c:202 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
bridge/java-foreign.c:214 |
| medium | opengrep/go.lang.security.audit.use-of-unsafe-block: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low] |
bridge/java-log.go:49 |
| medium | opengrep/go.lang.security.audit.use-of-unsafe-block: Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'r [confidence low] |
bridge/java-log.go:64 |
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: 104,990; test lines: 666
| Language | Lines |
|---|---|
| Objective-C | 65,924 |
| C | 17,179 |
| Go | 16,555 |
| Java | 3,570 |
| Python | 1,201 |
| Shell | 767 |
| Swift | 460 |
Coverage gaps
qual-complexity: /app/.venv/bin/python3 timed out after 900s