zvtvz/zvt

modular quant framework.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 16th, 2026
Created on April 4th, 2019
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 1,015
Total Stargazers: 4,309 (+0)
Total Subscribers: 140 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.6 days
Mean response time: 152.8 days
90th percentile: 433.5 days
Tracked items: 23

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 464 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

zvt is a modular quantitative trading framework that enables developers to build, backtest, and deploy algorithmic trading strategies across multiple asset classes.

The framework addresses the complexity of quantitative finance by providing a modular architecture that separates concerns into distinct components for data fetching, indicator calculation, strategy definition, and backtesting. This modular design allows developers to mix and match components, reuse logic across different strategies, and extend functionality without modifying core code. The tool supports multiple data sources and asset types including stocks, cryptocurrencies, and other instruments, making it suitable for researchers and traders working across different markets.

The project suits developers who need a flexible foundation for quantitative research rather than a rigid, opinionated platform. It works well for teams building custom trading systems where modularity and extensibility matter more than out-of-the-box simplicity. The framework includes support for technical analysis, fundamental analysis, and machine learning integration, allowing strategies to combine multiple analytical approaches. Those choosing this tool should expect to invest time understanding its architecture and building on top of its components rather than relying on pre-built strategies.

Development activity shows consistent engagement with the codebase through regular commits addressing bug fixes and feature additions. The project maintains active issue tracking with responses to user questions and problem reports. Pull requests are reviewed and merged regularly, indicating ongoing maintenance and evolution of the framework. Documentation is actively maintained alongside code changes to reflect current functionality and usage patterns.