How audit_script() detects calls | What gets skipped | Single-file vs directory scan | Version resolution | The audit_report object | How risk_score() works | Check 1: "changelog" — the breaking-changes database | Check 2: "seed_check" — missing set.seed() | Check 3: "locale_check" — locale-sensitive operations | Combining checks and filtering | Working with the results | Practical interpretation

The problem they solve — a real scenario | Scenario — The revision drift problem | certify() — creating a baseline | What gets hashed | Choosing what to certify | Tags and the certification store | list_certs() — inspecting the store | check_drift() — comparing against a baseline | Basic usage | The four statuses | Using "latest" | Using drift results programmatically | Recommended workflow | At submission | After reviewer comments | Version control

What belongs in the database | Examples of things that belong | Examples of things that do not belong | The database schema | The version window | Rules for setting to_version | Quick reference | Risk levels | Finding candidates | From NEWS.md files | From your own experience | Writing an entry | Testing your entry | Submitting a pull request | Minimum test for a new entry | Keeping the database current

repro_report() — generating reports | The verdict | Style: "minimal" | Style: "academic" | Style: "pharma" | Format: "md" and "html" | All nine combinations | repro_badge() — status badges | Badge colours | Inserting into README.md | Removing a badge | Full CI pipeline

What is reproducr? | Why this matters — real failure modes | Scenario 1 — The collaborator upgrade problem | Scenario 2 — The server deployment problem | Scenario 3 — The renv false sense of security | Tier 1: Scan and score | Auditing a script | Scoring for risk | Tier 2: Baseline and drift detection | Certifying outputs | Checking for drift | Tier 3: Report and export | The full pipeline

How audit_script() detects calls | What gets skipped | Single-file vs directory scan | Version resolution | The audit_report object | How risk_score() works | Check 1: "changelog" — the breaking-changes database | Check 2: "seed_check" — missing set.seed() | Check 3: "locale_check" — locale-sensitive operations | Combining checks and filtering | Working with the results | Practical interpretation

The problem they solve — a real scenario | Scenario — The revision drift problem | certify() — creating a baseline | What gets hashed | Choosing what to certify | Tags and the certification store | list_certs() — inspecting the store | check_drift() — comparing against a baseline | Basic usage | The four statuses | Using "latest" | Using drift results programmatically | Recommended workflow | At submission | After reviewer comments | Version control

repro_report() — generating reports | The verdict | Style: "minimal" | Style: "academic" | Style: "pharma" | Format: "md" and "html" | All nine combinations | repro_badge() — status badges | Badge colours | Inserting into README.md | Removing a badge | Full CI pipeline

What is reproducr? | Why this matters — real failure modes | Scenario 1 — The collaborator upgrade problem | Scenario 2 — The server deployment problem | Scenario 3 — The renv false sense of security | Tier 1: Scan and score | Auditing a script | Scoring for risk | Tier 2: Baseline and drift detection | Certifying outputs | Checking for drift | Tier 3: Report and export | The full pipeline

What belongs in the database | Examples of things that belong | Examples of things that do not belong | The database schema | The version window | Rules for setting to_version | Quick reference | Risk levels | Finding candidates | From NEWS.md files | From your own experience | Writing an entry | Testing your entry | Submitting a pull request | Minimum test for a new entry | Keeping the database current