Getting noticed, but rough fundamentals could turn visitors away.
Python-based quant trading research project for short-term reversal option setups, universe selection, staged-entry backtesting, and live paper trading.
Documentation
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
0
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 26Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 250Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files43 root entries
- assets
- results
- scripts
- versions
- .gitignoreGood: .gitignore present.
- analyze_reversal_2_4_overfitting.py
- analyze_reversal_3_1_regime_predictive_power.py
- backtest_metrics.py
- backtest_reversal_2_2_1_calls.py
- backtest_reversal_2_3_1_calls.py
- backtest_reversal_2_3_3_calls.py
- backtest_reversal_2_3_calls.py
- backtest_reversal_2_4_calls.py
- backtest_reversal_2_5_calls.py
- backtest_reversal_2_5_min_drop_experiment.py
- backtest_reversal_3_1_calls.py
- backtest_reversal_3_1_leveraged_etf_experiment.py
- backtest_reversal_3_3_calls.py
- backtest_reversal_3_3_target_exit_experiment.py
- backtest_reversal_3_3_timing_overlay_experiment.py
- backtest_reversal_article_variants.py
- compare_reversal_2_3_1_universes.py
- compare_reversal_2_3_3_universes.py
- LICENSEGood: Licensed under Other.
- plot_reversal_3_1_regime_score_dark.py
- plot_theme.py
- qqq_only_filtered_tickers.csv
- qqq_plus_leverage_etfs_tickers.csv
- qqq_tickers.txt
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- RESEARCH_GUARDRAILS.md
- reversal_3_2_1_live.py
- reversal_3_3_live.py
- reversal_3_4_1_alpaca_paper.py
- reversal_universe.py
- Reversal3.2.3.ipynb
- Reversal3.3.ipynb
- SECURITY.mdGood: Security policy present.
- spy_tickers.txt
- success_rate_comparison.png
- universe_tickers.csv
- update_reversal_csv.ipynb
- update_reversal_data.py