Skip to content

google/gson · Java

Google's JSON serialization library for Java. Mature, focused, widely deployed.

Source: google/gson · commit abfef5e · scanned 2026-05-23

You

Analyze google/gson (Java) at commit abfef5e for technical debt. Summarize severity distribution, top rules triggered, and SQALE rating.

tech-debt-mcp

Scanned 602 issues in 358ms.

At a glance

IssuesSQALE ratingRemediationScan time
602A22d 13h 20m358ms

Severity distribution

criticalhighmediumlow
06049745

Top rules triggered

RuleSeverityCount
suppress-warningsmedium371
nesting-depthhigh146
file-lengthhigh22
todo-commentlow17
deprecated-no-infolow17
catch-generic-exceptionmedium11
system-outlow9
empty-catchhigh6

Raw scan data: gson.json

You

What kind of debt is this? Show the SQALE breakdown by category.

tech-debt-mcp · get_sqale_metrics (full scan — no maxFiles cap)

Remediation time by debt category — where the work would land if you fixed everything:

CategoryRemediation
maintainability42d
code-quality25d 3h
documentation1h

The bulk of remediation lives in maintainability — that's where a debt-reduction sprint would have the highest ROI.

You

Show me the worst issues — top high-severity findings with file paths.

tech-debt-mcp · get_issues_by_severity (derived from full scan — combined high + critical)

Top 5 high-severity findings:

SeverityRuleLocation
highnesting-depthextras/src/main/java/com/google/gson/typeadapters/RuntimeTypeAdapterFactory.java:278
highnesting-depthextras/src/test/java/com/google/gson/interceptors/InterceptorTest.java:118
highnesting-depthextras/src/test/java/com/google/gson/typeadapters/PostConstructAdapterFactoryTest.java:43
highfile-lengthgson/src/main/java/com/google/gson/Gson.java
highfile-lengthgson/src/main/java/com/google/gson/GsonBuilder.java
You

What dependencies does it use?

tech-debt-mcp · check_dependencies
text
# 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
You

What should I fix first?

tech-debt-mcp · get_recommendations (simplified view — title + description from AnalysisEngine.analyzeProject())
  1. Clean Up TODO/FIXME Comments — Found 17 TODO/FIXME comments. Consider creating tracked issues.

  2. Dedicate Time for Tech Debt Reduction — 60 high-severity issues found. Consider allocating sprint time for tech debt.

  3. Improve Code Maintainability — Several files have maintainability issues like deep nesting or excessive length.

You

How do I reproduce this locally?

tech-debt-mcp

Clone the repo at the pinned commit:

bash
git clone https://github.com/google/gson.git
cd gson && git checkout abfef5e8455483b878a8dea14dd42fa55832a56c

Option 1 — npx (any MCP client)

Add to your client's MCP config:

json
{
  "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@techdebtmcp

Then 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.