These repositories are published because the work is more useful in the open than in a private tree. Issues and pull requests are welcome, with the expectations below.
Issues are reviewed on a monthly cadence. A slow reply is normal and is not a signal that the report was unwelcome.
Reports of false positives or false negatives in aeo-scan checks. The scanner makes structural claims about real pages, so a check that misfires is a defect worth fixing. Include the page HTML — or the smallest reduction that still reproduces it — along with the command you ran and the output you got.
- Open an issue first for anything beyond an obvious defect fix, so effort is not spent on a change that turns out to be off-scope.
- Keep the
aeo-scancore dependency-free. Site-specific behavior belongs inaeo-scan.config.json, not in the core. - Include a test for any behavior change, and run the existing suite before pushing.
- One logical change per pull request.
aeo-standard is versioned, and changes to scoring are deliberate. If a criterion looks wrong, unmeasurable, or double-counted, open an issue there rather than a pull request against the scanner — the scanner follows the standard, not the other way around.
Contributions to aeo-scan are accepted under MIT, and contributions to aeo-standard and whitepapers under CC BY 4.0. Do not submit material you do not have the right to license, and do not include credentials, client data, or internal URLs in issues or pull requests.