finvizfinance

Finviz analysis python library.

Runssource: GitHubhomepagePythonMITcommit 44ded722ae9d

Python, MIT licensed. The project labels itself: crypto, earnings calls, financial analysis, forex, fundament, fundamental analysis, inside trader and outer ratings.

finvizfinance runs. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

finvizfinance v1.5.0 installed and builds. Quote, calendar, insider, news, group overview, crypto, forex, and futures all verified working against live finviz.com. Screener and earnings remain broken due to finviz SPA migration requiring a larger rewrite.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.62 (measured)
recorded runs
2
last tested
stars
1,790
forks
291
open issues
0
watchers
29
size
7 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing finvizfinance, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • crypto, forex, future, calendar Drift (finviz site migrated to SPA)7 minutes
  • screener/earnings Drift - cannot fix fully3 minutes
  • test fixtures outdated for new JSON format2 minutes
  • pip install failed (externally-managed-environment on system python)1 minute
Install time
14 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
scripts/live_smoke.py reported 8 OK, 0 DRIFT, 0 ERROR. pytest test/ reported 128 passed, 13 skipped. Live tests: 11/13 passed (screener/earnings still Drifted).
Model tokens used
426,994
Exact commit tested
44ded722ae9d
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

OK    group                     11 rows
OK    crypto                    40 rows
OK    forex                     10 rows
OK    futures                   60 rows
FAIL  earnings                  Failed to parse finviz response: required element 'earnings screene…
Total time: 3.3s
Now let me produce the final JSON:
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
 succeeded in 0ms:
tokens used
426,994

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 14 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.62
Argusic Runner1/3Runs with mocks92.000.01

Topics (from GitHub)

cryptoearnings-callsfinancial-analysisforexfundamentfundamental-analysisinside-traderouter-ratingspandaspypiscreenerstock-chartsstock-newstechnical-analysisweb-scraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/finvizfinance.svg)](https://argusic.com/subject/finvizfinance)

Questions

Does finvizfinance run?
Yes. finvizfinance runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test finvizfinance?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 44ded722ae9d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test finvizfinance?
The run that produced this verdict cost $0.62: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does finvizfinance take to install?
14 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does finvizfinance need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing finvizfinance?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for finvizfinance?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion