FlanChanXwO/phpwind-captcha-dataset

PHPWind Captcha Dataset

Labelled four-digit numeric captcha images for training and evaluating OCR on authorized PHPWind deployments. This repository stores each visual captcha family in an independent dataset directory so that samples from different versions, forks, themes, or generators are never silently mixed.

中文说明: README_zh.md

Related model: FlanChanXwO/phpwind-captcha-ocr

Dataset catalogue

legacy-footer-v0.7-beta is the training-data scope for the related model's published reference metric. It does not establish compatibility with other PHPWind releases, forks, themes, or captcha generators.

Repository layout

datasets/
├── index.json                         # Catalogue of published dataset directories
└── legacy-footer-v0.7-beta/
    ├── metadata.json                  # Source/version boundary and dataset properties
    ├── labels.json                    # Filename-to-label mapping
    └── images/                        # Captcha PNG files

Every future version-specific dataset must use the same isolated layout:

datasets/phpwind-v7/
├── metadata.json
├── labels.json
└── images/

Do not place v7, v8, custom-theme, or fork samples in legacy-footer-v0.7-beta/images/. Give each visually distinct generator its own directory and catalogue entry.

Current dataset details

labels.json is an object keyed by filename. Each entry contains the final four-digit label, the recorded votes, the number of votes (count), and the agreement flag (agreed). Image paths are relative to the dataset directory: images/<filename>.

{
  "b1_0000.png": {
    "label": "9125",
    "votes": ["9125"],
    "count": 1,
    "agreed": true
  }
}

Adding a new version-specific dataset

1. 1.Create datasets/<dataset-id>/images/; use a distinct ID such as phpwind-v7 or phpwind-v8 only when that version has been established from authorized evidence.
2. 2.Add only that generator's images and a separate labels.json. Keep the image filenames unique inside its own directory.
3. 3.Add metadata.json with the observed version or deployment identifier, captcha format, image count, collection provenance, and any known visual customization. Do not infer an official version from a theme footer alone.
4. 4.Add the dataset to datasets/index.json and update the catalogue table above. Record whether its labels have been independently reviewed.
5. 5.Train and evaluate each version separately first. Combine datasets only in an explicitly documented multi-version experiment with per-version results.

Responsible use and license

Use only captcha images from deployments you own or are explicitly authorized to test. Do not use this dataset to automate account logins or bypass access controls. The dataset is released under GNU AGPL-3.0.