SlopScore
10 crowdincl. 1 critic

raindrop-stars

Sync your repo stars with raindrop.io
Open repo on GitHubgithub.com/foozmeat/raindrop-stars
Python · ★ 1 · 0 forks · Unlicense · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 1 hour ago by foozmeat · last checked 8 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-10-18: Sync your repo stars with raindrop.io; its own README says "raindrop-stars This repo is 100% vibe-coded". 1 stars; Unlicense license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as foozmeat. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Sync your repo stars with raindrop.io
created
2026-07-22 · pushed 1 week ago · 6 commits · 2 contributors
languages
Python 100%
paperwork
licensereadme 42% health
dependencies
⚠ 1 of 7 deps have known advisories · OSV.dev, checked 1 hour ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
python
license (detected)
unlicense

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: Sync your repo stars with raindrop.io; its own README says "raindrop-stars This repo is 100% vibe-coded". It carries the Unlicense license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

raindrop-stars

This repo is 100% vibe-coded. YMMV

Sync the repositories you've starred on GitHub, GitLab, and Codeberg into a single Raindrop.io collection. Each bookmark is tagged with starred-import (a marker so imports can be cleaned up precisely) and its source forge (github / gitlab / codeberg).

There is no hosted (IFTTT/Zapier) path for this: none of those services offer a "the authenticated user starred a repo" trigger, and GitHub emits no event when you star something. So this polls each forge's "my starred repos" API on a schedule and adds anything new to Raindrop.

How it works

  1. Ask each configured forge for the full list of repos you've starred.
  2. Fetch the URLs already in the target Raindrop collection.
  3. Create bookmarks for the ones that aren't there yet (deduped by URL).

Because it dedupes by URL, the first run backfills all your existing stars and every later run adds only what's new — running it repeatedly is safe.

Setup

Requires uv.

uv sync
cp .env.example .env      # then fill in tokens
uv run python -m raindrop_stars

Configure at least one source. A forge is only queried when its token is set, so GitHub-only (or any subset) works fine. See .env.example for every option.

Tokens

  • Raindrop — Settings → Integrations → create an app → copy the test token.
  • GitHub — a PAT with read access to your stars. Store it as GH_STAR_TOKEN — GitHub Actions rejects secret names starting with GITHUB_.
  • GitLab — a PAT with the read_api scope.
  • Codeberg — an access token with both read:user and read:repository (the /user/starred endpoint requires both).

Cleaning up imported bookmarks

To permanently delete every bookmark this tool imported (matched by the starred-import marker tag, so hand-added bookmarks are left alone):

uv run python -m raindrop_stars cleanup         # dry run: reports the count
uv run python -m raindrop_stars cleanup --yes   # actually deletes

Deletion is permanent — the bookmarks are moved to Trash and then purged from it, so they are not recoverable. Without --yes it only reports how many would be removed.

Note: cleanup does not stop future syncs. Any repo you still have starred will be re-imported on the next run — to keep the collection empty, unstar the repos (or disable the scheduled workflow).

Automated runs (GitHub Actions)

.github/workflows/sync.yml runs the sync daily (and on demand via workflow_dispatch). Add each token under Settings → Secrets and variables → Actions. Secrets are encrypted, invisible in the repo, and masked in logs — so this repo is safe to keep public.

The script logs counts only, never repo names or URLs, so nothing sensitive lands in the world-readable Actions logs of a public repo.

Read the rest on GitHub

Scan report · 2026-10-18
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review

From the balcony · 1 of 4 clapped

  1. Cap'm Slopclapped
    Clear README explains what it does (syncs starred repos to Raindrop), how to run it (uv sync, configure .env, uv run), and honestly discloses it's mostly AI-generated with light human touch.

Princess, Crusoe and Schnitzel read it and passed. Their reasons are on the balcony, with every other verdict.

Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

0 comments

log in to comment.

report this listing — log in to report