Free domain registration and practical DNS learning resources for everyone.
This report summarizes scanner evidence for DigitalPlatDev/FreeDomain, a Markdown project with 203,348 GitHub stars. SynthScan examined 7,345 lines of code across 77 source files, recording 48 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 11.2 (Moderate pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 48 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 48 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 48 distinct pattern matches across 1 syntactic category. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | documents/tutorial/website/3.5-deploy-and-connect.md | 5 | ## Step 1: Back Up the Current Site | COMMENT |
| LOW | documents/tutorial/website/3.5-deploy-and-connect.md | 9 | ## Step 2: Copy the Files | COMMENT |
| LOW | documents/tutorial/website/3.5-deploy-and-connect.md | 26 | ## Step 3: Create DNS Records | COMMENT |
| LOW⚡ | documents/tutorial/website/3.5-deploy-and-connect.md | 56 | ## Step 4: Verify DNS | COMMENT |
| LOW⚡ | documents/tutorial/website/3.5-deploy-and-connect.md | 66 | ## Step 5: Verify HTTP | COMMENT |
| LOW⚡ | documents/tutorial/website/3.5-deploy-and-connect.md | 75 | ## Step 6: Choose the Canonical Hostname | COMMENT |
| LOW | documents/tutorial/capstone/7.2-build-and-test.md | 5 | ## Step 1: Create the Project | COMMENT |
| LOW | documents/tutorial/capstone/7.2-build-and-test.md | 28 | ## Step 2: Create the Home Page | COMMENT |
| LOW | documents/tutorial/capstone/7.2-build-and-test.md | 65 | ## Step 3: Create the About Page | COMMENT |
| LOW | documents/tutorial/capstone/7.2-build-and-test.md | 102 | ## Step 4: Create the Stylesheet | COMMENT |
| LOW | documents/tutorial/capstone/7.2-build-and-test.md | 216 | ## Step 5: Run the Local Server | COMMENT |
| LOW | documents/tutorial/capstone/7.2-build-and-test.md | 224 | ## Step 6: Functional Tests | COMMENT |
| LOW⚡ | documents/tutorial/capstone/7.2-build-and-test.md | 241 | ## Step 7: Accessibility Tests | COMMENT |
| LOW⚡ | documents/tutorial/capstone/7.2-build-and-test.md | 251 | ## Step 8: Content and Privacy Review | COMMENT |
| LOW⚡ | documents/tutorial/capstone/7.2-build-and-test.md | 261 | ## Step 9: Save the Baseline | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 5 | ## Step 1: Prepare the DNS Zone | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 11 | ## Step 2: Register the Domain | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 26 | ## Step 3: Verify Delegation | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 43 | ## Step 4: Prepare the Server | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 61 | ## Step 5: Deploy Files | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 82 | ## Step 6: Configure Nginx | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 114 | ## Step 7: Test Before DNS | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 123 | ## Step 8: Add DNS Records | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 154 | ## Step 9: Verify Public HTTP | COMMENT |
| LOW | documents/tutorial/capstone/7.3-register-and-deploy.md | 166 | ## Step 10: Record the Change | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 15 | ## Step 1: Write the Project Statement | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 29 | ## Step 2: Define the Pages | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 47 | ## Step 3: Select Names | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 68 | ## Step 4: Assign Owners | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 88 | ## Step 5: Draw the Architecture | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 115 | ## Step 6: Define Public Data | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 135 | ## Step 7: Define Completion Evidence | COMMENT |
| LOW | documents/tutorial/capstone/7.1-project-brief.md | 156 | ## Step 8: Write the Rollback Plan | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 5 | ## Step 1: Issue a Certificate | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 20 | ## Step 2: Verify HTTPS Directly | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 40 | ## Step 3: Configure Canonical Redirects | COMMENT |
| LOW⚡ | documents/tutorial/capstone/7.4-secure-and-operate.md | 64 | ## Step 4: Verify the Redirect Path | COMMENT |
| LOW⚡ | documents/tutorial/capstone/7.4-secure-and-operate.md | 72 | ## Step 5: Test Certificate Renewal | COMMENT |
| LOW⚡ | documents/tutorial/capstone/7.4-secure-and-operate.md | 78 | ## Step 6: Apply Server Baseline | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 95 | ## Step 7: Create a Website Backup | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 104 | ## Step 8: Restore in Isolation | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 116 | ## Step 9: Create Monitors | COMMENT |
| LOW | documents/tutorial/capstone/7.4-secure-and-operate.md | 129 | ## Step 10: Run a Failure Drill | COMMENT |
| LOW⚡ | documents/tutorial/dns/2.4-troubleshooting.md | 5 | ## Step 1: Confirm the Exact Name and Type | COMMENT |
| LOW⚡ | documents/tutorial/dns/2.4-troubleshooting.md | 13 | ## Step 2: Check Parent Delegation | COMMENT |
| LOW⚡ | documents/tutorial/dns/2.4-troubleshooting.md | 21 | ## Step 3: Check Every Authoritative Server | COMMENT |
| LOW⚡ | documents/tutorial/dns/2.4-troubleshooting.md | 30 | ## Step 4: Query the Record Directly | COMMENT |
| LOW⚡ | documents/tutorial/dns/2.4-troubleshooting.md | 38 | ## Step 5: Compare Recursive Answers | COMMENT |