tech-stack-evaluator
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTechnology Stack Evaluator
技术栈评估工具
Evaluate and compare technologies, frameworks, and cloud providers with data-driven analysis and actionable recommendations.
通过数据驱动的分析和可落地的建议,对技术、框架和云供应商进行评估与对比。
When to Use
适用场景
- You need to compare frameworks, cloud providers, or technology stacks across cost, ecosystem, security, or migration criteria.
- You are preparing a migration recommendation or technology selection spreadsheet with TCO and risk factors.
- The decision requires structured scoring (ecosystem health, security, performance).
- 你需要从成本、生态系统、安全性或迁移标准等维度对比框架、云供应商或技术栈
- 你正在准备包含TCO和风险因素的迁移建议或技术选型表格
- 决策需要结构化评分(如生态系统健康度、安全性、性能)
When NOT to Use
不适用场景
- The request is for a quick coding question or implementation detail unrelated to evaluating tech stacks.
- The situation involves a single technology with no comparison or migration decision.
- You only need a high-level opinion without structured analysis or evidence.
- 请求是与技术栈评估无关的快速编码问题或实现细节
- 场景仅涉及单一技术,无需对比或迁移决策
- 你只需要无结构化分析或证据支撑的高层级观点
Table of Contents
目录
Capabilities
功能特性
| Capability | Description |
|---|---|
| Technology Comparison | Compare frameworks and libraries with weighted scoring |
| TCO Analysis | Calculate 5-year total cost including hidden costs |
| Ecosystem Health | Assess GitHub metrics, npm adoption, community strength |
| Security Assessment | Evaluate vulnerabilities and compliance readiness |
| Migration Analysis | Estimate effort, risks, and timeline for migrations |
| Cloud Comparison | Compare AWS, Azure, GCP for specific workloads |
| 功能 | 描述 |
|---|---|
| 技术对比 | 通过加权评分对比框架和库 |
| TCO分析 | 计算包含隐性成本在内的5年总成本 |
| 生态系统健康度 | 评估GitHub指标、npm采用率、社区活跃度 |
| 安全性评估 | 评估漏洞情况和合规就绪度 |
| 迁移分析 | 估算迁移的工作量、风险和时间线 |
| 云服务商对比 | 针对特定工作负载对比AWS、Azure、GCP |
Quick Start
快速开始
Compare Two Technologies
对比两种技术
Compare React vs Vue for a SaaS dashboard.
Priorities: developer productivity (40%), ecosystem (30%), performance (30%).Compare React vs Vue for a SaaS dashboard.
Priorities: developer productivity (40%), ecosystem (30%), performance (30%).Calculate TCO
计算TCO
Calculate 5-year TCO for Next.js on Vercel.
Team: 8 developers. Hosting: $2500/month. Growth: 40%/year.Calculate 5-year TCO for Next.js on Vercel.
Team: 8 developers. Hosting: $2500/month. Growth: 40%/year.Assess Migration
评估迁移可行性
Evaluate migrating from Angular.js to React.
Codebase: 50,000 lines, 200 components. Team: 6 developers.Evaluate migrating from Angular.js to React.
Codebase: 50,000 lines, 200 components. Team: 6 developers.Input Formats
输入格式
The evaluator accepts three input formats:
Text - Natural language queries
Compare PostgreSQL vs MongoDB for our e-commerce platform.YAML - Structured input for automation
yaml
comparison:
technologies: ["React", "Vue"]
use_case: "SaaS dashboard"
weights:
ecosystem: 30
performance: 25
developer_experience: 45JSON - Programmatic integration
json
{
"technologies": ["React", "Vue"],
"use_case": "SaaS dashboard"
}评估工具支持三种输入格式:
文本 - 自然语言查询
Compare PostgreSQL vs MongoDB for our e-commerce platform.YAML - 用于自动化的结构化输入
yaml
comparison:
technologies: ["React", "Vue"]
use_case: "SaaS dashboard"
weights:
ecosystem: 30
performance: 25
developer_experience: 45JSON - 程序化集成
json
{
"technologies": ["React", "Vue"],
"use_case": "SaaS dashboard"
}Analysis Types
分析类型
Quick Comparison (200-300 tokens)
快速对比(200-300词)
- Weighted scores and recommendation
- Top 3 decision factors
- Confidence level
- 加权评分与建议
- 三大决策因素
- 置信度等级
Standard Analysis (500-800 tokens)
标准分析(500-800词)
- Comparison matrix
- TCO overview
- Security summary
- 对比矩阵
- TCO概览
- 安全性摘要
Full Report (1200-1500 tokens)
完整报告(1200-1500词)
- All metrics and calculations
- Migration analysis
- Detailed recommendations
- 所有指标与计算过程
- 迁移分析
- 详细建议
Scripts
脚本
stack_comparator.py
stack_comparator.py
Compare technologies with customizable weighted criteria.
bash
python scripts/stack_comparator.py --help通过可自定义的加权标准对比技术。
bash
python scripts/stack_comparator.py --helptco_calculator.py
tco_calculator.py
Calculate total cost of ownership over multi-year projections.
bash
python scripts/tco_calculator.py --input assets/sample_input_tco.json计算多年周期内的总拥有成本。
bash
python scripts/tco_calculator.py --input assets/sample_input_tco.jsonecosystem_analyzer.py
ecosystem_analyzer.py
Analyze ecosystem health from GitHub, npm, and community metrics.
bash
python scripts/ecosystem_analyzer.py --technology react从GitHub、npm和社区指标分析生态系统健康度。
bash
python scripts/ecosystem_analyzer.py --technology reactsecurity_assessor.py
security_assessor.py
Evaluate security posture and compliance readiness.
bash
python scripts/security_assessor.py --technology express --compliance soc2,gdpr评估安全态势与合规就绪度。
bash
python scripts/security_assessor.py --technology express --compliance soc2,gdprmigration_analyzer.py
migration_analyzer.py
Estimate migration complexity, effort, and risks.
bash
python scripts/migration_analyzer.py --from angular-1.x --to react估算迁移复杂度、工作量和风险。
bash
python scripts/migration_analyzer.py --from angular-1.x --to reactReferences
参考资料
| Document | Content |
|---|---|
| Detailed scoring algorithms and calculation formulas |
| Input/output examples for all analysis types |
| Step-by-step evaluation workflows |
| 文档 | 内容 |
|---|---|
| 详细的评分算法与计算公式 |
| 所有分析类型的输入/输出示例 |
| 分步式评估工作流 |
Confidence Levels
置信度等级
| Level | Score | Interpretation |
|---|---|---|
| High | 80-100% | Clear winner, strong data |
| Medium | 50-79% | Trade-offs present, moderate uncertainty |
| Low | < 50% | Close call, limited data |
| 等级 | 分数 | 说明 |
|---|---|---|
| 高 | 80-100% | 结果明确,数据支撑充分 |
| 中 | 50-79% | 存在取舍,不确定性中等 |
| 低 | < 50% | 难分伯仲,数据有限 |
When to Use
适用场景
- Comparing frontend/backend frameworks for new projects
- Evaluating cloud providers for specific workloads
- Planning technology migrations with risk assessment
- Calculating build vs. buy decisions with TCO
- Assessing open-source library viability
- 为新项目对比前端/后端框架
- 针对特定工作负载评估云供应商
- 结合风险评估规划技术迁移
- 通过TCO分析决定自研还是采购
- 评估开源库的可行性
When NOT to Use
不适用场景
- Trivial decisions between similar tools (use team preference)
- Mandated technology choices (decision already made)
- Emergency production issues (use monitoring tools)
- 相似工具间的琐碎决策(可参考团队偏好)
- 已强制指定的技术选型(决策已确定)
- 生产环境紧急问题(使用监控工具)