B

Code Dependency Usage Analyzer

3.30

Derivation Chain

Step 1 Emergence of unused code detection tools (rev-dep)
→
Step 2 Rising maintenance costs for large-scale monorepos
→
Step 3 SaaS for automating unused dependency removal + cost savings reporting

Problem

Development teams running monorepos with 100+ packages typically find that 15-25% of all dependencies are unused, yet they leave them in place out of fear of breaking builds. These unused dependencies increase CI/CD build times by 20-40%, raise false positives in security vulnerability scans, and waste an average of 10 developer-hours per month.

Solution

A SaaS that integrates with GitHub/GitLab repos to automatically analyze dependency graphs, identify unused or underused packages, simulate the impact of removal, and auto-generate safe removal PRs. Monthly reports quantify post-removal savings in build time and image size.

Target: DevOps / Platform Engineering teams at IT companies (20-200 employees) running monorepos
Revenue Model: SaaS monthly subscription: up to 5 repos at ~$44/mo (~59,000 KRW), up to 20 repos at ~$112/mo (~149,000 KRW), unlimited at ~$224/mo (~299,000 KRW). Distributed via GitHub Marketplace.
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (63%)

Tech Complexity
29.3/40
Data Availability
13.8/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (56/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
7.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] Data Pipeline [medium] Frontend [low]
Dashboard