zxh0/jvm.go
A toy JVM written in Go
- Repository: https://github.com/zxh0/jvm.go
- Commit:
129b147ebcc820279748f6095c916da1986ebef1 - Generated: 2026-11-13T23:22:29+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 | 69 | adequate | 90% | 100% |
| Security | 74 | 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 |
|---|---|---|
| 2015-05 | 783 | 0% |
| 2015-11 | 1,984 | 0% |
| 2015-12 | 627 | 0% |
| 2017-03 | 3 | 0% |
| 2017-11 | 10 | 0% |
| 2018-12 | 4 | 0% |
| 2019-05 | 536 | 0% |
| 2019-07 | 271 | 0% |
| 2019-09 | 6,826 | 0% |
| 2019-10 | 8,563 | 0% |
| 2019-11 | 439 | 0% |
| 2019-12 | 11 | 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 adequate: test-to-source ratio 0.29, no CI test run detected; 6% of function code in complex or long functions; 2% duplicated lines. Weakest area: process.
| Area | Score |
|---|---|
| Complexity (lizard) | 84 |
| Duplication | 89 |
| Code smells (Opengrep) | 97 |
| Tests and CI | 60 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | 0 |
- Functions: 1,281; mean complexity 1.9, 90th percentile 3; 3 complex and 1 long functions
- Duplicated lines: 2.0% of 9,744 compared
- Tests: 4,237 test lines for 14,580 source lines (ratio 0.29); CI test commands: none detected; 25% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- newInstruction in instructions/factory.go: complexity 205, 414 lines
- readConstantInfo in classfile/constant_info.go: complexity 17, 39 lines
- describeModule in cmd/jmod/main.go: complexity 16, 48 lines
Security
Security posture is adequate: 3 known vulnerabilities in 1 dependencies. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 91 |
| Vulnerable dependencies (OSV) | 88 |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | 22 |
-
Known vulnerabilities: 3 in 1 packages (critical 0, high 1, medium 2, low 0)
-
Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
-
OpenSSF Scorecard aggregate: 1.9/10 (published 2026-11-09)
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | osv/GHSA-6q6q-88xp-6f2r: gopkg.in/[email protected] (Go) is affected by GO-2022-0956, GHSA-6q6q-88xp-6f2r |
go.sum |
| 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] |
native/java/lang/Object.go:45 |
| 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] |
native/java/lang/System.go:84 |
| 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] |
native/sun/misc/Unsafe_cas.go:99 |
| 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] |
native/sun/misc/Unsafe_cas.go:102 |
| 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] |
native/sun/misc/Unsafe_cas.go:103 |
| 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] |
rtda/class_initialization.go:17 |
| 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] |
vmutils/native_endian.go:15 |
| 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] |
vmutils/native_endian.go:20 |
| 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] |
vmutils/native_endian.go:25 |
| 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] |
vmutils/unsafe.go:10 |
| 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] |
vmutils/unsafe.go:14 |
| 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] |
vmutils/unsafe.go:20 |
| 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] |
vmutils/unsafe.go:25 |
| 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] |
vmutils/unsafe.go:31 |
| 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] |
vmutils/unsafe.go:37 |
| medium | osv/GHSA-wxc4-f4m6-wwqv: gopkg.in/[email protected] (Go) is affected by GO-2020-0036, GHSA-wxc4-f4m6-wwqv |
go.sum |
| medium | osv/GHSA-r88r-gmrh-7j83: gopkg.in/[email protected] (Go) is affected by GO-2021-0061, GHSA-r88r-gmrh-7j83 |
go.sum |
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: 14,580; test lines: 4,237
| Language | Lines |
|---|---|
| Go | 15,352 |
| Java | 3,449 |
| Shell | 16 |