google/gson · Java
Google's JSON serialization library for Java. Mature, focused, widely deployed.
Source:
google/gson· commitabfef5e· scanned 2026-05-23
Analyze google/gson (Java) at commit abfef5e for technical debt. Summarize severity distribution, top rules triggered, and SQALE rating.
Scanned 602 issues in 358ms.
At a glance
| Issues | SQALE rating | Remediation | Scan time |
|---|---|---|---|
| 602 | A | 22d 13h 20m | 358ms |
Severity distribution
| critical | high | medium | low |
|---|---|---|---|
| 0 | 60 | 497 | 45 |
Top rules triggered
| Rule | Severity | Count |
|---|---|---|
suppress-warnings | medium | 371 |
nesting-depth | high | 146 |
file-length | high | 22 |
todo-comment | low | 17 |
deprecated-no-info | low | 17 |
catch-generic-exception | medium | 11 |
system-out | low | 9 |
empty-catch | high | 6 |
Raw scan data: gson.json
What kind of debt is this? Show the SQALE breakdown by category.
Remediation time by debt category — where the work would land if you fixed everything:
| Category | Remediation |
|---|---|
| maintainability | 42d |
| code-quality | 25d 3h |
| documentation | 1h |
The bulk of remediation lives in maintainability — that's where a debt-reduction sprint would have the highest ROI.
Show me the worst issues — top high-severity findings with file paths.
Top 5 high-severity findings:
| Severity | Rule | Location |
|---|---|---|
| high | nesting-depth | extras/src/main/java/com/google/gson/typeadapters/RuntimeTypeAdapterFactory.java:278 |
| high | nesting-depth | extras/src/test/java/com/google/gson/interceptors/InterceptorTest.java:118 |
| high | nesting-depth | extras/src/test/java/com/google/gson/typeadapters/PostConstructAdapterFactoryTest.java:43 |
| high | file-length | gson/src/main/java/com/google/gson/Gson.java |
| high | file-length | gson/src/main/java/com/google/gson/GsonBuilder.java |
What dependencies does it use?
# Dependency Analysis
**Project:** td-showcase-google-gson-abfef5e84554-1779575568213
**Found:** 8 package file(s) across 1 ecosystem(s)
**Total Dependencies:** 25
**Ecosystems:** gradle
## extras/pom.xml (gradle)
**Dependencies:** 2
### Production (2)
- com.google.code.gson:gson@2.14.1-SNAPSHOT
- javax.annotation:jsr250-api@1.0
## gson/pom.xml (gradle)
**Dependencies:** 5
### Production (3)
- com.google.errorprone:error_prone_annotations@2.48.0
- com.guardsquare:proguard-base@7.8.2
- com.guardsquare:proguard-core@9.3.2
### Development (2)
- com.google.guava:guava-testlib@33.5.0-jre
- com.google.guava:guava@33.5.0-jre
## metrics/pom.xml (gradle)
**Dependencies:** 3
### Production (3)
- com.google.code.gson:gson@${project.parent.version}
- com.fasterxml.jackson.core:jackson-databind@2.21.1
- com.google.caliper:caliper@1.0-beta-3
## pom.xml (gradle)
**Dependencies:** 3
### Production (3)
- junit:junit@4.13.2
- com.google.truth:truth@1.4.5
- ${project.groupId}:${project.artifactId}@0.0.0-JAPICMP-OLD
## proto/pom.xml (gradle)
**Dependencies:** 5
### Production (3)
- com.google.code.gson:gson@${project.parent.version}
- com.google.protobuf:protobuf-java@${protobufVersion}
- com.google.guava:guava@33.5.0-jre
### Development (2)
- com.google.truth.extensions:truth-proto-extension@1.4.5
- com.google.testparameterinjector:test-parameter-injector@1.22
## test-graal-native-image/pom.xml (gradle)
**Dependencies:** 2
### Production (2)
- org.junit:junit-bom@6.0.3
- com.google.code.gson:gson@${project.parent.version}
## test-jpms/pom.xml (gradle)
**Dependencies:** 1
### Production (1)
- com.google.code.gson:gson@${project.parent.version}
## test-shrinker/pom.xml (gradle)
**Dependencies:** 4
### Production (4)
- com.google.code.gson:gson@${project.parent.ver
…What should I fix first?
Clean Up TODO/FIXME Comments — Found 17 TODO/FIXME comments. Consider creating tracked issues.
Dedicate Time for Tech Debt Reduction — 60 high-severity issues found. Consider allocating sprint time for tech debt.
Improve Code Maintainability — Several files have maintainability issues like deep nesting or excessive length.
How do I reproduce this locally?
Clone the repo at the pinned commit:
git clone https://github.com/google/gson.git
cd gson && git checkout abfef5e8455483b878a8dea14dd42fa55832a56cOption 1 — npx (any MCP client)
Add to your client's MCP config:
{
"mcpServers": {
"tech-debt": { "command": "npx", "args": ["-y", "tech-debt-mcp@latest"] }
}
}Then call analyze_project with the absolute path to the clone.
Option 2 — Claude Code plugin
/plugin marketplace add PierreJanineh/TechDebtMCP
/plugin install tech-debt-mcp@techdebtmcpThen ask Claude Code: "Run analyze_project on this directory."
Spot a false positive?
Open an issue with the showcase-fp label and link this page. Existing reports for google/gson.
Tech Debt MCP is a static analyzer. It identifies patterns that often indicate debt — not all flagged code is broken, and not all debt will be flagged. Repository authors are not responsible for these findings.