Javstash Autofill

suzuhiroruri · July 12, 2026, 11:45pm


	Summary	On performer create, fill empty fields from a scraper (best name match, skip if none). Existing values/images are protected; per-field overwrite is optional. Primary name can be the created one or the scraper’s, chosen separately for Identify and manual; when the scraper name would collide, the new performer is merged into the existing one.
	Repository	https://github.com/stashapp/CommunityScripts/tree/main/plugins/javstashAutofill
	Source URL	https://stashapp.github.io/CommunityScripts/stable/index.yml
	Install	How to install a plugin?

Javstash Autofill

Automatically fills in a newly-created performer’s empty fields from a scraper (default: the javstash stash-box) the moment the performer is created (Performer.Create.Post hook).

It searches the configured source by the performer’s name, takes the best name-matching candidate, and fills the empty fields. Existing values and existing images are protected by default; you can opt into overwriting on a per-field basis.

Behaviour

Best name match, or skip. The candidate with the highest name-match score (exact = 1.0, otherwise fuzzy) is used. If the best score is below the configurable threshold, nothing is done.
Fill empty only (default). Only empty fields are written, so manual edits and other scrapers’ data are preserved. Each field can be switched to “overwrite existing” individually.
Primary name policy. For each origin (Identify vs. manual creation) you can choose whether the created name stays primary (scraper name goes to aliases) or the scraper’s canonical name becomes primary (created name goes to aliases).
Duplicate merge. When the scraper name would become primary but a performer with that name already exists, the newly-created one is merged into the existing performer (performerMerge) — scenes are re-linked, the created name and the stash-box id are carried over, and the duplicate is removed.
Measurements normalisation. 91H-56-88 → 91(H)-56-88.
Asynchronous image. The image is downloaded and set in a detached background process, so the hook returns immediately and Stash never blocks on a slow remote image fetch.

Requirements

Python 3 available to Stash’s plugin runner.
The chosen source configured in Stash. For a stash-box source (e.g. javstash), add it under Settings → Metadata Providers → Stash-box Endpoints.

Settings

Setting	Description
Scraper (Identify) / Scraper (manual)	Source per origin: a stash-box endpoint URL or a `scraper_id`. Empty = javstash.
Use scraper name (Identify) / (manual)	Make the scraper’s canonical name the primary name for that origin. Default: Identify ON, manual OFF.
Name-match threshold	Skip if the best match score is below this (default 0.9).
Overwrite: field	Per-field toggle. OFF = fill only when empty (default); ON = overwrite even if a value already exists. For URLs / aliases, ON replaces and OFF appends; for the image, ON replaces an existing image.

Notes

The source scrape is proxied through Stash’s own scrapeSinglePerformer, so no API keys are needed in the plugin itself.
Identify-origin creations are detected by the presence of stash_ids in the create input.

DogmaDragon · September 7, 2026, 8:38am

github.com/stashapp/CommunityScripts

fix(javstashAutofill): correct name casing, store the stash-box id, simplify the source setting

main ← dude-stash:javstash-autofill-fixes

opened 02:30AM - 07 Sep 26 UTC

dude-stash

+119 -32

Fixes #773. Three fixes for Javstash Autofill, version bumped to 1.4. ### 1. Th…e name is now corrected to the scraper's spelling I usually type performer names without the right casing, and the plugin never fixed them. The rename check was: ```python prefer_scraper = bool(use_scraper_name) and bool(cand_name) and norm(cand_name) != norm(name) ``` `norm()` lowercases and strips spaces, so `yua mikami` and `Yua Mikami` are equal there and nothing happens. Now: ```python same_name = norm(cand_name) == norm(name) prefer_scraper = (bool(cand_name) and nfc(cand_name) != nfc(name) and (bool(use_scraper_name) or same_name)) ``` A difference in casing or spacing is always corrected, because it is the same name. A really different name still needs the "use scraper name as primary" toggle, as before. `find_by_name()` compares with `norm()` now as well, so an existing "Yua Mikami" is found as the duplicate and merged, instead of the rename hitting it. ### 2. The stash-box id is stored `remote_site_id` was missing from the scrape query, so the id was never available. It is requested now and, when the source is a stash-box, written into `stash_ids` in all three paths (fill, rename, merge), without touching ids from other endpoints. Identify and the Tagger recognise the performer after autofill. `urls` was added to the query too, because `build_update()` was reading `cand.get("url")` and that field was never fetched. ### 3. The source setting no longer needs the endpoint URL Before, the setting wanted the full endpoint URL that Stash already has under Settings → Metadata Providers. Worse, `resolveStashBox` only accepts an endpoint that matches a configured one exactly, so a trailing slash or a small typo failed with "stash box not found" and the hook only logged a scrape error. `resolve_source()` now looks the value up in `configuration.general.stashBoxes` and `listScrapers(types: [PERFORMER])`, in this order: 1. stash-box name, e.g. `StashDB` 2. exact endpoint URL 3. any URL, passed through as before 4. part of a name or endpoint, e.g. `stashdb` 5. performer scraper id or name, e.g. `Minnano-AV-JP` Empty uses javstash if it is configured, otherwise the first configured stash-box. The log line now says which source was used, for example `via stash-box 'StashDB' (by name)`. Old values keep working: a full URL and a `scraper_id` are still accepted, so nobody has to change their settings. ### Testing - Tested against my own library: a manually created performer typed in lowercase gets the correct name, the StashDB id in `stash_ids`, and the fields filled. - The source resolution and the update building were also checked with a stubbed GraphQL client for every case listed above, including a stash-box that is not configured and a scraper name that does not exist. - `node validate.js plugins/javstashAutofill/javstashAutofill.yml` passes. README and CHANGELOG updated. AI assistance was used for this change.

@suzuhiroruri would you be interested in reviewing it?