SlopScore
00 crowd

book-recommender

A machine learning project that recommends your next favorite book using collaborative filtering and content based filtering.
Open repo on GitHub Open the demogithub.com/saricmilos/book-recommender
Jupyter Notebook · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 1 hour ago by saricmilos · last checked 1 hour 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-12: A machine learning project that recommends your next favorite book using collaborative filtering and content b; its own README says "The last three v1 commits (October 2026) were made with Claude Code while tidying the repository: committing local work, limiting CORS and u". 1 stars; MIT 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 saricmilos. 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
A machine learning project that recommends your next favorite book using collaborative filtering and content based filtering.
website
https://saricmilos.com/book-recommender/
created
2025-11-04 · pushed 6 hours ago · 98 commits · 1 contributor
languages
Jupyter Notebook 98%Python 2%Dockerfile 0%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · 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)
dockerfilejupyter-notebookpython
license (detected)
mit

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: A machine learning project that recommends your next favorite book using collaborative filtering and content b; its own README says "The last three v1 commits (October 2026) were made with Claude Code while tidying the repository: committing local work, limiting CORS and u". It carries the MIT 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

Book Recommender

Book recommendations learned from the Book-Crossing ratings: 1,149,780 ratings by 278,858 users on 271,360 books (Kaggle, Book Recommendation Dataset).

The repository holds two versions of the project. v1 is kept exactly as I built it by hand. v2 is being built beside it with Claude Code, on the same data, and will be measured against v1 on the same test split.

v1 v2
Built by hand, November 2025 to early 2026 with Claude Code, from October 2026: I set the goals, review every change and check the evaluation
Code v1/, and tag v1.0 for the original layout v2/
Status frozen in progress

v1

v1's files are as they were; they only moved into v1/. The last three v1 commits (October 2026) were made with Claude Code while tidying the repository: committing local work, limiting CORS and updating paths. The notebooks read the data from an absolute path on the machine they were written on; to run them, point dataset_folder at datasets/.

v2

Built in stages, each measured on the same test split as v1. v2/README.md says how to run it and what each stage found.

  1. Evaluation, done (report): v1 reproduces exactly from its own code, and v1 is scored again next to simple baselines. v1's user-based model, as shipped, recommends best so far: 27.7% of users find one of their held-out books in its top 10, against 14.9% for the most popular books.
  2. Data quality: clean titles, merge editions of the same book, fetch book details once.
  3. Models: use the implicit interactions (62.3% of the ratings are 0, meaning a book was seen but not rated), add content embeddings for books with few ratings, and combine both.
  4. A demo on saricmilos.com that needs no server.

Data

datasets/ holds Books.csv, Ratings.csv and Users.csv. Both versions read them and neither changes them.

License

MIT

Read the rest on GitHub

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

From the balcony · 0 of 4 clapped

    Crusoe, Schnitzel, Cap'm Slop and Princess 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