Scweet
Twitter scraper and X scraper for Python: scrape tweets, profiles, followers, following and trends without the official API. Twitter scraping library with multi-account pooling, proxy support and async, or a hosted version on Apify.
Runs with mockssource: GitHubhomepagePythonMITcommit 295138808e9f
Python, MIT licensed. The project labels itself: apify, python, python library, scrape tweets, tweet scraper, tweets, twitter and twitter api.
Scweet runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Scweet 5.8.0 installed from source, all 495 unit tests pass, CLI help works, package imports correctly. The library requires real X accounts and auth tokens for live scraping.
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 92 of 100 (the mean of this project's run scores).
At a glance
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.
- Install time
- under a minute
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pip install completed; python3 -m pytest tests/ -q --ignore=tests/test_integration.py exited 0 with 495 passed, 1 skipped in ~129s; python3 -m Scweet --help printed help text with all subcommands; python3 -c 'from Scweet import Scweet; Scweet(auth_token="test")' created object successfully
- Model tokens used
- 87,453
- Exact commit tested
- 295138808e9f
- 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
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 758ms: <string>:1: RuntimeWarning: Account provisioning produced no usable accounts. The auth_token is usu… Scweet object created OK That's expected — it warns about no usable accounts because we passed a test token, but the object … exec /bin/sh -lc 'cd /work/repo && python3 -c "from Scweet import __version__; print(__version__)" 2>&1'… succeeded in 247ms: 5.8.0 Everything works. Here's the report: tokens used 87,453 Everything works. Here's the report:
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
- Installed in 0.3 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.04 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
apifypythonpython-libraryscrape-tweetstweet-scrapertweetstwittertwitter-apitwitter-crawlertwitter-datatwitter-followerstwitter-scrapertwitter-scrapingtwitter-searchtwitter-trendsweb-scrapingxx-apix-scraperx-twitter
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scweet)Questions
- Does Scweet run?
- Scweet runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test Scweet?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 295138808e9f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Scweet?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Scweet take to install?
- 0.3 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 Scweet need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Scweet?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for Scweet?
- 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.