Driftguard — A compliance linter for OKF v0.2, tested against the official reference bundles! #228
jpjoshua
started this conversation in
Show and tell
Replies: 1 comment
|
Something worth noting for anyone comparing options: there's also thisismydesign/okf-lint, which covers similar §11 conformance ground for v0.1. The difference here is that Drifgaurd supports v0.2 — stale_after, status, and verified trust tiers are not yet in that tool (no shade I promise). Therefore, Driftguard addresses staleness/trust directly from the spec's own fields, rather than requiring separate tooling for that purpose. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I built a small checker for OKF bundles since I didn't see one in the repo yet. It implements the §11 conformance rules (frontmatter validity, required type, reserved-file structure when present) plus the new v0.2 lifecycle fields — stale_after, status, verified trust tiers.
It tested clean against all four official reference bundles (ga4, stackoverflow, crypto_bitcoin, acme_retail)!!! It showed zero false positives across 78 files then verified it correctly catches broken frontmatter, missing type, malformed log.md, and passed stale_after dates on synthetic test cases. Full test report's is in the repo to review.
Its desigend toships as a Claude Code plugin, or run as a standalone script.
python3 okf_lint.py /path/to/your/bundleHere is the Repo: Driftgaurd Github
I also set up a weekly check that watches for spec version changes and re-validates automatically, since v0.1 → v0.2 already happened once in only six weeks.
All reactions