jryan5150/.github — community health defaults

This is GitHub's community health repository for @jryan5150. The files here propagate as defaults to any of my repositories that don't ship their own version.

What lives here

.github/
├── profile/
│   └── README.md              ← shows on github.com/jryan5150
│
├── README.md                  ← (this file) shows when someone visits this repo
│
└── .github/
    ├── CONTRIBUTING.md         ← default contributor guide for any repo
    ├── CODE_OF_CONDUCT.md      ← Contributor Covenant 2.1
    ├── SECURITY.md             ← default security policy + reporting path
    ├── SUPPORT.md              ← where to get help across my projects
    ├── FUNDING.yml             ← sponsorship config (currently disabled)
    ├── PULL_REQUEST_TEMPLATE.md
    └── ISSUE_TEMPLATE/
        ├── bug_report.md
        ├── feature_request.md
        └── config.yml          ← disables blank issues, sets contact links

How GitHub uses these defaults

For each of my repos:

• If the repo has its own CONTRIBUTING.md → GitHub uses the repo's own
• If it doesn't → GitHub auto-uses the one from this .github repo

Same propagation rule for CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md, issue templates, and PR templates.

What does NOT propagate: GitHub Actions workflows, .gitignore, LICENSE. These need to be in each repo individually.

Why this exists

Before this repo existed, every new project of mine started without OSS-hygiene scaffolding. CONTRIBUTING.md, security policy, issue templates — all retroactively bolted on after I noticed they were missing. This repo flips the default: every future repo of mine starts hygienic from day one. A reviewer landing on a fresh jryan5150/<new-project> repo gets the same baseline community-health surface as my flagship public repos.

This is a small instance of the Four-Layer Context Architecture methodology applied to GitHub presence — Layer 2 (rules) for OSS hygiene, propagated as defaults rather than re-derived per-repo.

Per-repo overrides

Repos with domain-specific needs override these defaults:

• gone-phishing — ships its own CONTRIBUTING.md (focus areas, BYOM adapter contribution paths), SECURITY.md (security tool with explicit reporting flow + supported-version table), and a playbook_contribution.md issue template specific to NIST 800-61 playbook submissions
• claude-harness-starter — ships its own CONTRIBUTING.md (no-philosophy scope constraint), specific missing_example.md and identity_review.md issue templates, and a PR template that enforces the scope check

Default templates here cover everything else.

License

The templates and configuration in this repo are CC0 / public domain. Use them, fork them, change them — no attribution required.

The profile README content (profile/README.md) is © 2026 Jace Ryan, all rights reserved (since it's autobiographical content, not template).