Automated SourceForge Weekly Download Scorecard
Every Monday, WebRun opens SourceForge, compiles the past week's download counts by release file and any new tickets or reviews, texts the maintainer through Twilio a short summary of the headline numbers, and saves a full CSV export to Google Drive so the download history is easy to review later.
How do I track weekly SourceForge downloads and activity?
WebRun compiles your SourceForge project's weekly downloads and new tickets every Monday. It texts the maintainer through Twilio a short summary of the headline numbers, and saves a full CSV export to Google Drive, so download history is easy to review later and nothing about the week's activity gets missed.
- Download and ticket trends are tracked automatically every week
- A permanent CSV record builds up for reporting or grant applications
- The maintainer gets a summary without logging in to check manually
Built for open source maintainers · project maintainers · community managers · indie developers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
sourceforge.net/user/loginin a real browser with your saved login - no setup, no API keys. -
1
SourceForge - compile the week's downloads and tickets
- Open SourceForge and pull the past week's download counts by release file
- Count new tickets and reviews posted this week
- Compare this week's downloads against last week's
Done when The week's downloads by file and new ticket count are captured.
-
2
Twilio - text the maintainer the summary
twilio.com
WebRun opens Twilio to text the maintainer the summary. - Text the maintainer a short summary of this week's total downloads and new tickets
- Note the week over week change in downloads
- Send it once, after the full numbers are compiled
Done when The maintainer has this week's summary text.
-
3
Google Drive - save the export
drive.google.com
WebRun opens Google Drive to save the export. - Save a CSV export of this week's downloads and tickets to the project folder
- Name the file with the week's date range
- Keep a running folder so download history is easy to review
Done when This week's CSV export is saved to Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it respond to tickets or reviews itself?
No. WebRun only counts and reports new tickets and reviews. Responding to them is always done by the maintainer.
Why a CSV export every week?
So there's a permanent, downloadable record of download history outside SourceForge itself, useful for grant reports or just tracking growth over time.
What if there were no downloads or tickets that week?
The text still goes out reporting a quiet week, so you know the check ran and nothing was missed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.