Tracking issue for bringing this repository to 100% compliance with KofTwentyTwo/standards (commit 855cf44, pre-1.0 draft) in the 1.0.1 release. The full audit (168 requirement ids: 52 compliant, 50 partial, 36 non-compliant) is summarized in the sub-issues below.
Plan
Ordered as the standards README prescribes: settings, then security workflows, then repository files, then formatting, then analyzers. Every file change arrives as a Conventional-Commit, DCO-signed PR against main; settings and account items are the maintainer's.
#
Workstream
Standard ids
Who
1
CI and security workflows: pr-gates, security, codeql, scorecard callers; hardened ci/release/nuget-updates; scanner configs; Dependabot cooldown; SBOM, SHA256SUMS, CC release notes, LICENSE in assets
Kingsrook C# style: standard .editorconfig, Directory.Build.props, central package management, LF, global.json, Meziantou, reformat, SPDX headers, one type per file, PowerShell style and analyzer
Maintainer-only items and the merge order are on #66; the v1.0.1 release checklist is #67. Agents stop at the pull request (K22-AI-10): merging, the ruleset changes, and the tag are yours.
## Implementation status (2026-10-09)
| PR | Workstream | Checks |
| --- | --- | --- |
| #68 | ci: standards gates, hardened workflows, SBOM, SHA256SUMS, CC release notes | all green |
| #69 | docs: README/SECURITY/CONTRIBUTING/templates, CoC, CLAUDE.md, 6 ADRs, threat model | all green (stacked on #68) |
| #70 | style: Kingsrook layout, standard editorconfig/props, CPM, LF, SPDX, one type per file, PowerShell | green except `pr / dependency-review` (file-licensed packages; fixed by standards PR #4) |
| #71 | ci: retire superseded gates (draft; after the ruleset edit) | n/a |
| KofTwentyTwo/standards#4 | `allow-dependencies-licenses` input, DCO parsing fix, EX-0003/EX-0004, analyzer settings | pending |
Maintainer-only items and the merge order are on #66; the v1.0.1 release checklist is #67. Agents stop at the pull request (K22-AI-10): merging, the ruleset changes, and the tag are yours.
Shipped: v1.1.0 is the first stable release with the full standards adoption (shared signed Velopack workflow, provenance, SBOMs, signed+DCO commits, 100% coverage gates, FlaUI gate, smoke test of the published app, data root outside the install folder, default-token accounts, dev edition). Conformance was 0 FAIL at 3f05d54; remaining SHOULD-level items are the org-level ones on #66 (org .github repository, allowed-actions policy). Closing this epic is the owner's call once #66 is settled.
Shipped: v1.1.0 is the first stable release with the full standards adoption (shared signed Velopack workflow, provenance, SBOMs, signed+DCO commits, 100% coverage gates, FlaUI gate, smoke test of the published app, data root outside the install folder, default-token accounts, dev edition). Conformance was 0 FAIL at 3f05d54; remaining SHOULD-level items are the org-level ones on #66 (org .github repository, allowed-actions policy). Closing this epic is the owner's call once #66 is settled.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Tracking issue for bringing this repository to 100% compliance with KofTwentyTwo/standards (commit
855cf44, pre-1.0 draft) in the 1.0.1 release. The full audit (168 requirement ids: 52 compliant, 50 partial, 36 non-compliant) is summarized in the sub-issues below.Plan
Ordered as the standards README prescribes: settings, then security workflows, then repository files, then formatting, then analyzers. Every file change arrives as a Conventional-Commit, DCO-signed PR against
main; settings and account items are the maintainer's.pr-gates,security,codeql,scorecardcallers; hardenedci/release/nuget-updates; scanner configs; Dependabot cooldown; SBOM,SHA256SUMS, CC release notes, LICENSE in assets.editorconfig,Directory.Build.props, central package management, LF,global.json, Meziantou, reformat, SPDX headers, one type per file, PowerShell style and analyzer.github, retiringdev, exception-register entries, release checklist, access reviewConventions from here on
<type>/<description>offmain; PR titles are Conventional Commit headers; every commitgit commit -S -s.Sub-issues follow.
Implementation status (2026-10-09)
pr / dependency-review(file-licensed packages; fixed by standards PR #4)allow-dependencies-licensesinput, DCO parsing fix, EX-0003/EX-0004, analyzer settingsMaintainer-only items and the merge order are on #66; the v1.0.1 release checklist is #67. Agents stop at the pull request (K22-AI-10): merging, the ruleset changes, and the tag are yours.
Progress (2026-10-09, afternoon)
ae174f5ae174f5, license exemption input)CLEAN, awaiting maintainer mergepr / dependency-reviewwill pass once rebased onto #68's pin); awaiting the stack mergeprotect-mainrulesetprotect-release-tagsruleset.git-blame-ignore-revs,devretirement, context switchAll four stacked PRs (#68 → #69 → #70 → #71) are green and
CLEANas of 16:20 UTC; see #66 for the maintainer merge sequence.Shipped: v1.1.0 is the first stable release with the full standards adoption (shared signed Velopack workflow, provenance, SBOMs, signed+DCO commits, 100% coverage gates, FlaUI gate, smoke test of the published app, data root outside the install folder, default-token accounts, dev edition). Conformance was 0 FAIL at 3f05d54; remaining SHOULD-level items are the org-level ones on #66 (org .github repository, allowed-actions policy). Closing this epic is the owner's call once #66 is settled.