Skip to content
Projects

JoeKarlsson/bechdel-test has 30 GitHub stars and 6 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-15 12:53 UTC. Last push 2026-11-06.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
0
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Does your favorite film pass the test?

Web & Apps

README.md

Original

bechdel.io

Find out if your favorite film passes the test

Coverage Status Build Status Maintainability stars pr license twitter first-timers-only

The Bechdel Test, sometimes called the Mo Movie Measure or Bechdel Rule is a simple test which names the following three criteria

  1. It includes at least two women
  2. who have at least one conversation
  3. about something other than a man or men.

The test was popularized by Alison Bechdel's comic Dykes to Watch Out For, in a 1985 strip called The Rule. For a nice video introduction to the subject please check out The Bechdel Test for Women in Movies on feministfrequency.com.

This project analyzes movie scripts to see whether each film passes the Bechdel Test, and looks at several other feminist components of a film. It can answer questions like "How many females are in this film," "By what factor does this pass the Bechdel Test?"

How it works

The site at https://bechdel.joekarlsson.com/ is fully static: an Astro build in site/, deployed to GitHub Pages. There is no server or database. Films are added by running the analyzer locally and committing what it writes.

scripts/<title>.txt ──npm run analyze──▶ data/films/<id>.json ──site/ build──▶ GitHub Pages

For each script, npm run analyze looks the film up on OMDB, gets the cast and their genders from TMDB, scores the Bechdel Test from the script text, and (optionally) asks an AI model, through the homelab LiteLLM gateway, for a second opinion and a deeper read. See docs/ARCHITECTURE.md.

Add films

Needs Node 22 or later, API keys for OMDB and TMDB, and for the AI read a LiteLLM virtual key (on the LAN or over Tailscale).

git clone https://github.com/JoeKarlsson/bechdel-test
cd bechdel-test
npm install
cp .env.example .env    # then fill in the keys

npm run analyze                              # every scripts/*.txt not already on the site
npm run analyze -- scripts/heat.txt          # one film
npm run analyze -- --force scripts/heat.txt  # redo a film that's already on the site
npm run analyze -- --no-ai ...               # skip the AI read (a redone film keeps its old one)

It ends with a table of every script's film and score, so you can check each match before committing. If a title matches the wrong film, put the year in the file name (deep-cover-1992.txt). OMDB and TMDB responses are cached in .cache/; delete it to refetch.

Then publish: see DEPLOYMENT.md.

npm test       # the parser and analysis
npm run lint

Where to Get Movie Scripts?

If you are looking to get your hands on some movie scripts to test, you can check out my CLI Movie Script Grabber https://github.com/JoeKarlsson/movie-script-scraper

Introduction

The Bechdel Test Script Parser was a collaborative digital humanities project between myself and my sister, Laurel Karlsson. It is the product of a shared passion for film, feminism, and the creative potential of technology. By combining the talents and interests of myself, a software engineer, we've been able to create an innovative data mining tool for film analysis that we hope to continue to work on and improve. You can check out the project on our website.

This project was born when my sister reached out to me for advice on a few ideas she had been mulling over for a digital humanities project. Hoping to do something related to feminist film analysis, she was feeling very limited by my lack of coding experience and hadn't been able to find an existing data mining tool to accomplish what she was looking to do. I immediately offered up my coding expertise, looking to gain experience by building a tool from scratch which would accomplish the specific needs of the project. After brainstorming several different project ideas, we settled on the one you see here.

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

TLDR

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Maintainers


Joe Karlsson

Laurel Karlsson

License

MIT

Related Links

Resources