Bump github/codeql-action/init from d8073367669608af8fbcc5f63dd0a0d52bb90cff to 1c5b675653bb5c22dbe9b12b556ec555138e09fd

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,22 @@
+name: Something on the site is wrong
+description: A wrong number, a dead link, or a page that does not render
+labels: ["bug"]
+body:
+  - type: input
+    id: page
+    attributes:
+      label: Which page
+      placeholder: https://dkautomation23.github.io/ucp-survey.html
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: What is wrong
+      description: For a wrong number, say what it should be and how you know.
+    validations:
+      required: true
+  - type: input
+    id: browser
+    attributes:
+      label: Browser and screen width, if it is a layout problem

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question, or paid work
+    url: mailto:hello@dkautomation.dev
+    about: Anything that is not a bug report or a feature request
+  - name: Security report
+    url: https://github.com/dkautomation23/.github/blob/main/SECURITY.md
+    about: Report a vulnerability privately, never in a public issue

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,15 @@
+name: Suggest something
+description: A page that would be worth having, or data worth publishing
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: idea
+    attributes:
+      label: What would you want to find here?
+    validations:
+      required: true
+  - type: textarea
+    id: why
+    attributes:
+      label: Who would use it, and for what?
+      description: This site publishes measurements, not opinions.

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: "/"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5

.github/workflows/codeql.yml

@@ -0,0 +1,31 @@
+# GitHub's own static analysis, reading the paths the tests do not.
+#
+# Findings appear under Security -> Code scanning. A false positive is
+# dismissed with a written reason, never by deleting the query.
+name: CodeQL
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: '0 6 * * 1'
+permissions:
+  contents: read
+  security-events: write
+jobs:
+  analyze:
+    name: analyze (${{ matrix.language }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        language: ['javascript-typescript']
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
+      - uses: github/codeql-action/init@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4
+        with:
+          languages: ${{ matrix.language }}
+          queries: security-extended
+      - uses: github/codeql-action/autobuild@d8073367669608af8fbcc5f63dd0a0d52bb90cff # v4
+      - uses: github/codeql-action/analyze@d8073367669608af8fbcc5f63dd0a0d52bb90cff # v4

CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at hello@dkautomation.dev. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing
+
+This is a personal site, so pull requests that change its wording or its claims
+will usually be declined. Two kinds of change are welcome:
+
+- **A factual correction.** If a number, a date or a claim on the site is
+  wrong, open an issue with the evidence. Published numbers are meant to be
+  checkable; being wrong in public is worse than being corrected.
+- **A broken page.** Layout that fails at some width, a dead link, a page that
+  does not render.
+
+## Working on it
+
+No dependencies to install. Node 22 or newer:
+
+```console
+$ node build.mjs
+$ node survey.mjs ../ucp-audit/survey/2026-09-18-aggregate.json
+$ python -m http.server 8765      # then open http://127.0.0.1:8765
+```
+
+Generated files (`tools/*.html`, `ucp-survey.html`, `sitemap.xml`) are committed,
+so run the generator and commit its output rather than editing the result.
+
+Never hand-edit a number on a page. It comes from the aggregate file the audit
+wrote; if it is wrong, the run is wrong, and that is what gets fixed.

README.md

@@ -0,0 +1,34 @@
+# dkautomation23.github.io
+
+The site at <https://dkautomation23.github.io>: a page per tool, plus the
+open-data pages.
+
+Everything is static and generated by two scripts with Node's standard library
+and nothing else.
+
+## Building it
+
+```console
+$ node build.mjs                                   # a page per tool, plus sitemap.xml
+$ node survey.mjs ../ucp-audit/survey/<date>-aggregate.json   # the survey page
+```
+
+`build.mjs` reads `tools.json`. `survey.mjs` reads the aggregate a real audit
+run wrote, so a number that is not in that file cannot appear on the page.
+
+## What is where
+
+| Path | What it is |
+|---|---|
+| `index.html` | the front page, edited by hand |
+| `tools.json` | one entry per tool; `build.mjs` turns each into a page |
+| `survey.mjs` | builds `ucp-survey.html` from measured data |
+| `style.css` | the whole stylesheet |
+| `sitemap.xml`, `robots.txt` | generated and committed |
+
+## Rules this site keeps
+
+- No tracking, no analytics, no cookies. There is nothing to consent to.
+- Every published number names its method, its date and the script that
+  produced it.
+- Shop names from the survey never reach this repository — only totals.

SECURITY.md

@@ -0,0 +1,26 @@
+# Security policy
+
+This repository is a static site. There is no server, no database and no user
+input: GitHub Pages serves files from the default branch.
+
+## Reporting
+
+**Security → Report a vulnerability** on this repository, or
+**hello@dkautomation.dev**. First reply within 2 working days.
+
+Do not open a public issue for a security problem.
+
+## In scope
+
+- Content injection: anything that makes a published page execute code or load
+  a resource the repository does not contain.
+- A page or a data file that exposes personal data. The survey publishes totals
+  only, and a shop name appearing anywhere on the site is a bug worth reporting.
+- A link or a redirect that sends a visitor somewhere other than where it says.
+
+## Out of scope
+
+- Missing security headers that GitHub Pages does not let a site set.
+- The absence of a Content Security Policy header, for the same reason; the
+  pages load no third-party script.
+- Findings about GitHub Pages itself — report those to GitHub.

build.mjs

@@ -136,6 +136,7 @@ const urls = [
   // The survey is the only page here that is data rather than a tool, and the
   // one most likely to be linked to from elsewhere.
   { loc: `${SITE}/ucp-survey.html`, priority: "0.9" },
+  { loc: `${SITE}/security-txt-survey.html`, priority: "0.9" },
   ...tools.map((tool) => ({ loc: `${SITE}/tools/${tool.slug}.html`, priority: "0.8" })),
 ];
 writeFileSync(

index.html

@@ -45,6 +45,12 @@ <h1>Dmytro Galko</h1>
   <div class="wrap">
     <h2>Open data — what AI shopping agents actually see</h2>
 
+    <div class="tool">
+      <h3><a href="security-txt-survey.html">Half the security.txt files at the top of the web are invalid</a></h3>
+      <p>A <code>security.txt</code> tells a researcher where to report a hole in your site, and RFC 9116 makes its <code>Expires</code> field mandatory — an expired file is, in the words of the specification, as good as no file. Of the 158 such files among the 500 most visited sites, 92 carry no <code>Expires</code> at all and 6 have expired: 62% are not valid. Nothing warns when that happens.</p>
+      <p class="tags"><span>500 sites</span><span>2026-09-18</span><span>raw results published</span><span>repeatable in one command</span></p>
+    </div>
+
     <div class="tool">
       <h3><a href="ucp-survey.html">A census of 5,356 live Shopify storefronts</a></h3>
       <p>Google and Shopify published the Universal Commerce Protocol so an agent can read a shop and buy from it. Nobody had published a count of how many shops actually speak it, so I measured it: 98.9% publish a valid profile, every one of them on the current release, none with a blocker. The only thing they differ on is whether an agent may sign the shopper into their own account — and 47.5% do not allow it, which turns a returning customer into an anonymous visitor.</p>
@@ -60,25 +66,25 @@ <h2>Command-line tools — Rust</h2>
     <div class="tool">
       <h3><a href="tools/csvdiff.html">csvdiff</a></h3>
       <p>Diffs two CSV exports by key and reports what actually changed. Two million rows in 2.8 seconds, a per-column breakdown with counted transitions, and number/null normalisation — so a migration report reads as 9 809 real changes instead of 995 000 rows of timestamp noise.</p>
-      <p class="tags"><span>Rust</span><span>13 tests</span><span>benchmark in repo</span><span>prebuilt binaries</span></p>
+      <p class="tags"><span>Rust</span><span>16 tests</span><span>benchmark in repo</span><span>prebuilt binaries</span></p>
     </div>
 
     <div class="tool">
       <h3><a href="tools/leakscan.html">leakscan</a></h3>
       <p>Offline check of what leaves with a file before you send it: tracked changes with the deleted text still readable, review comments, hidden worksheets, PDF attachments, GPS coordinates in photos, validated card and IBAN numbers.</p>
-      <p class="tags"><span>Rust</span><span>38 tests</span><span>no network at any point</span></p>
+      <p class="tags"><span>Rust</span><span>41 tests</span><span>no network at any point</span></p>
     </div>
 
     <div class="tool">
       <h3><a href="https://github.com/dkautomation23/imgdupe">imgdupe</a></h3>
       <p>Perceptual-hash duplicate finder. Complete-linkage grouping, so unrelated pictures never chain together through a path of small steps — and it writes a delete script for you to read instead of deleting anything itself.</p>
-      <p class="tags"><span>Rust</span><span>19 tests</span><span>benchmark in repo</span></p>
+      <p class="tags"><span>Rust</span><span>23 tests</span><span>benchmark in repo</span></p>
     </div>
 
     <div class="tool">
       <h3><a href="https://github.com/dkautomation23/linkscan">linkscan</a></h3>
       <p>Crawls a site and reports the links that are genuinely broken, keeping bot protection and slow third parties out of the "broken" column — which is why the report still gets read after the second run.</p>
-      <p class="tags"><span>Rust</span><span>15 tests</span><span>exit code for CI</span></p>
+      <p class="tags"><span>Rust</span><span>28 tests</span><span>exit code for CI</span></p>
     </div>
   </div>
 </section>
@@ -90,13 +96,19 @@ <h2>Integration tooling — TypeScript</h2>
     <div class="tool">
       <h3><a href="tools/webhook-rewind.html">webhook-rewind</a></h3>
       <p>Record the webhooks a provider sends you once, then replay them at your own code as often as you need — re-signed for Meta, GitHub, Shopify or Stripe, so the receiver runs its real verification instead of having it switched off for the debugging session.</p>
-      <p class="tags"><span>TypeScript</span><span>34 tests</span><span>no runtime dependencies</span></p>
+      <p class="tags"><span>TypeScript</span><span>35 tests</span><span>no runtime dependencies</span></p>
+    </div>
+
+    <div class="tool">
+      <h3><a href="tools/well-known-audit.html">well-known-audit</a></h3>
+      <p>A site publishes a dozen small files at its root — <code>security.txt</code>, <code>robots.txt</code>, <code>llms.txt</code>, <code>assetlinks.json</code>, <code>mta-sts.txt</code> — each checked by a different tool or by nobody. This reads all of them in one run and says which are missing, malformed, or quietly expired. RFC 9116 gives <code>security.txt</code> an <code>Expires</code> date; past it, the file is no longer valid, and almost nobody notices.</p>
+      <p class="tags"><span>TypeScript</span><span>106 tests</span><span>no runtime dependencies</span><span>refuses private addresses</span></p>
     </div>
 
     <div class="tool">
       <h3><a href="tools/ucp-audit.html">ucp-audit</a></h3>
       <p>Google and Shopify's Universal Commerce Protocol lets AI agents shop: every business publishes a profile at <code>/.well-known/ucp</code> and agents read it to decide what they can do. The failure mode is silence — offer checkout without declaring a searchable catalogue and no agent ever surfaces your products. This reads the profile the way an agent does.</p>
-      <p class="tags"><span>TypeScript</span><span>53 tests</span><span>no runtime dependencies</span><span>refuses private addresses</span></p>
+      <p class="tags"><span>TypeScript</span><span>59 tests</span><span>no runtime dependencies</span><span>refuses private addresses</span></p>
     </div>
 
     <div class="tool">
@@ -108,7 +120,7 @@ <h3><a href="tools/cra-report.html">cra-report</a></h3>
     <div class="tool">
       <h3><a href="tools/api-drift.html">api-drift</a></h3>
       <p>Records the shape of a JSON API and reports when it changes: removed fields, changed types, values that can now be null. Exits non-zero in CI, so a partner's silent rename stops being something you find out about two weeks later.</p>
-      <p class="tags"><span>TypeScript</span><span>29 tests</span><span>runs in cron or CI</span></p>
+      <p class="tags"><span>TypeScript</span><span>31 tests</span><span>runs in cron or CI</span></p>
     </div>
   </div>
 </section>