Trisk.R.Docker
F 49 completed
Other
containerized / r · tiny
38
Files
8,221
LOC
0
Frameworks
6
Languages
Pipeline State
completedRun ID
#1050968Phase
doneProgress
0%Started
2026-04-15 12:07:27Finished
2026-04-15 12:07:27LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
36.33Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:40Deduplication group #51636
Member of a group with 37 similar repo(s) — canonical #1208548 view group →
Provenance: Repobility (https://repobility.com) — every score reproducible from /scan/
AI Prompt
Create a self-contained, containerized application using Docker to run TRISK (Transition Risk Stress Testing) locally. The system needs to process financial data, specifically requiring input CSVs for the loan portfolio, company assets, and financial features. The goal is to assess the impact of climate transition scenarios on loan portfolios. The setup should be easily deployable using `docker-compose` and provide a web-based interface accessible at `http://localhost:3838/trisk/`. The code should be transparent and open-source.
r docker containerization finance stress-testing data-analysis web-app csv docker-compose
Generated by gemma4:latest
Catalog Information
Create a self-contained, containerized application using Docker to run TRISK (Transition Risk Stress Testing) locally. The system needs to process financial data, specifically requiring input CSVs for the loan portfolio, company assets, and financial features. The goal is to assess the impact of climate transition scenarios on loan portfolios. The setup should be easily deployable using docker-compose and provide a web-based interface accessible at http://localhost:3838/trisk/. The code shou
Tags
r docker containerization finance stress-testing data-analysis web-app csv docker-compose
Quality Score
F
49.1/100
Structure
59
Code Quality
12
Documentation
49
Testing
45
Practices
74
Security
90
Dependencies
50
Strengths
- CI/CD pipeline configured (github_actions)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Containerized deployment (Docker)
- Properly licensed project
Weaknesses
- 5 files with critical complexity need refactoring
- Potential hardcoded secrets in 1 files
- 1032 duplicate lines detected — consider DRY refactoring
- 4 'god files' with >500 LOC need decomposition
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
- Move hardcoded secrets to environment variables or a secrets manager
Languages
Frameworks
None detected
Symbols
variable3
Embed Badge
Add to your README:
