Directory / tyleree/jevbot

tyleree/jevbot

Options trading bot (backtest + Alpaca paper only) with TypeSafe Jev as the decision core

Reviewed New (under 90 days old) Bot 72/100

Not financial advice. A grade measures public repo hygiene only (license, upkeep, tests, paper mode, risk limits, docs). It does not measure returns, safety or suitability. Options trading can lose more than you invest. Read the full policy.

Reviewed. Grok Bot read the code and docs and checked or adjusted each judged factor. Nothing was executed. This is not a human audit. Reviewed on 2026-10-24 against commit 9dd5051, rubric v1.1.

Reviewer summary: Paper-only options bot with no live-money code path, a daily loss halt, a drawdown kill switch and an extensive test suite. No license file.

Facts

Repository	https://github.com/tyleree/jevbot
Type	Bot
Strategies	Not tagged
Brokers	Alpaca
License	No license
Language	Python
Last commit	2026-09-17 (37 days before the scan)
Last scanned	2026-10-24
Stars	5 (shown for context, never scored)

Score breakdown

Factor	Points	How it was decided
Risk limits and kill switch	20 / 20	config/default.toml has daily_loss_halt_pct, drawdown_kill_pct, max orders per minute and per-trade contract limits. Reviewer confirmed the scanner result. Scanner evidence (6, automated, can include false matches) `config/default.toml:106` [max loss] stop_loss_frac = 0.50 # close when loss >= 50% of max loss (long options: 50% of debit) `config/default.toml:168` [max orders] max_orders_per_minute = 10 # OPEN / discretionary CLOSE only; mandatory exits and KILL orders are exempt `src/jevbot/candidates.py:827` [max contracts] max_contracts = cfg.risk.max_contracts_per_trade `src/jevbot/eval/metrics.py:53` [max drawdown] "max_drawdown", `src/jevbot/risk.py:990` [stop loss] return ExitReason.STOP_LOSS `src/jevbot/state.py:729` [risk limit] them with our own risk limits); the state itself stays path-independent."""
License	0 / 15	No license file. Reviewer confirmed the scanner result.
Last commit on default branch	12 / 15	36 days since last commit Fact from the commit date, no judgment involved. Scanner evidence (1, automated, can include false matches) `default branch HEAD` 2026-09-18 (36 days ago)
Tests	10 / 15	1689 test cases found in 97 test files; CI test step not found Reviewer confirmed the scanner result. Scanner evidence (3, automated, can include false matches) `tests/conftest.py:1` 10 test cases `tests/fixtures/chain_factory.py:1` 9 test cases `tests/fixtures/fake_view.py:1` 6 test cases
Paper or dry-run mode	15 / 15	README states paper and backtests only; Alpaca clients are built with paper=True. Reviewer confirmed the scanner result. Scanner evidence (4, automated, can include false matches) `README.md:7` Paper trading and historical backtests only. There is no live-money code path, by design: Alpaca clients are `src/jevbot/cli/main.py:1` [paper-mode flag] """typer root: lazily registered sub-apps, global options, the PAPER-ONLY banner, exit codes (DESIGN.md sections 14 and 16). `src/jevbot/paper/alpaca_client.py:73` [paper endpoint] PAPER_BASE_URL: Final = "[link] `src/jevbot/paper/alpaca_client.py:12` [sandbox flag] \| `TradingClient(api_key, secret_key, paper=True)` \| `alpaca/trading/client.py::TradingClient.__init__`; `paper=True` selects `BaseURL.TRADI
README quality	5 / 10	install steps, 2078 chars Reviewer confirmed the scanner result. Scanner evidence (1, automated, can include false matches) `README.md:1` README with 2078 characters
Broker detection	10 / 10	Alpaca (deps, code, readme) Reviewer confirmed the scanner result. Scanner evidence (1, automated, can include false matches) `pyproject.toml:14` [Alpaca: deps+code+readme] "alpaca-py==0.44.0",
Total	72 / 100	Grades: A 85+, B 70+, C 55+, D 40+, F below.

Grades measure public repo hygiene on the scan date. They say nothing about profits, safety or security. We did not run this code. Full rubric and patterns.

Something wrong?

Report a correction Request removal (maintainers)

Corrections and removals are public GitHub issues. We reply within 7 days and every change is in the repo history. Sponsors get no special treatment: see our policy.

Badge for your README

Once the site has a public address, shields.io can read /badge/tyleree--jevbot.json from it. Badges show the grade and whether it was reviewed. Maintainers may use one without asking.