Field validation · public GitHub outcomes
CrossCheck field validation: what happened when 10 real repositories were reviewed
Two targeted follow-up waves turned static repository findings into ten public, repository-specific decisions: one owner-confirmed policy and self-implemented fix, four open pull requests, three open questions about maintainer intent, and two contributions deliberately avoided.
Published and last checked 21 September 2026
1
owner-confirmed, self-fixed
4
open value PRs
3
open intent questions
2
contributions avoided
Strongest public outcome
One ambiguous dual-lockfile state became an explicit pnpm-only policy
The owner of ageerle/ruoyi-web confirmed that pnpm is the only supported install path. The owner then authored and merged PR #38, removing package-lock.json, declaring the pnpm version, and aligning repository guidance and automation with that policy.
Exact interpretation: one repository owner answered the intent question and implemented their own cleanup. The public record resolves ambiguity into explicit repository policy. It does not show that the owner installed or ran CrossCheck, and it is not an adoption claim.
Method
Review the repository, then choose PR, question, or skip
- Step 1 - Re-check current repository state- Inspect the default branch, package manifests, lockfiles, CI, documentation, contribution rules, and relevant recent history.
- Step 2 - Separate evidence from intent- Treat coexisting configuration as a review prompt. Do not call it an error until repository-specific policy makes the intended state clear.
- Step 3 - Choose the least presumptive action- Open a narrow PR only when intent is explicit, ask a concise question when intent is ambiguous, and skip when the state is documented or already covered.
- Step 4 - Record public outcomes without upgrading them- An open PR is a proposed change, an open question is unresolved, and a merged maintainer-authored fix proves only the repository decision shown in its public thread.
The ten repositories were purposefully selected across two small distribution waves after the September benchmark correction. They were chosen for repository-specific follow-up value, not sampled to estimate a population rate. No third wave is included.
Public record
All 10 outcomes, with status frozen at the last check
Inspect or try it
Go from public evidence to your own repository
Start with the corrected benchmark and raw evidence, inspect the public source, or run CrossCheck against one repository. The GitHub Action is advisory by default; strict failure modes are explicit opt-ins and repository intent requires an explicit CrossCheck contract.
Limits and update policy
- • The set is small, purposefully selected, and unsuitable for estimating prevalence, acceptance rate, or CrossCheck adoption.
- • Four PRs and three questions remain open. Their descriptions are proposals or unresolved policy questions, not confirmed repository defects.
- • Public GitHub state can change after the stated last-checked date. The linked threads are authoritative for later reviews, merges, closures, or replies.
- • No revenue, install, scan, referral, or conversion outcome is attributed to these threads without direct observable evidence.
- • The raw September benchmark outputs remain frozen. This page reports later public follow-up outcomes; it does not rewrite the benchmark data.