help-wanted: co-maintainer

[ob-aion]

Bus factor 1. Pruner ships with a single maintainer. Apache-2.0, no commercial tier, no telemetry — see BUS_FACTOR.md.

A co-maintainer takes review burden off the critical path:

• Review pack rule proposals (docs/writing-rules.md, schema/rule-v1.json).
• Triage Dependabot bumps; each must pass scripts/verify-action-pins.sh.
• Cisco upstream-drift triage (7-day SLA on upstream-drift issues).
• FP-audit refresh per minor (docs/fp-audit.md).

Time commitment is irregular — rules-pack PRs are infrequent, Dependabot is weekly. Expect a few hours per month at the current cadence.

Profile: Python or YAML rule-pack literacy; familiarity with OWASP AST / LLM10 or Cisco's skill-scanner is a plus, not a requirement.

Interested contributors can comment below. CODEOWNERS update + branch protection grants follow.

[snakefood3232]

I see you're looking for a co-maintainer to review pack rules and manage Dependabot bumps. I'd handle this by closely following your guidelines in docs/writing-rules.md and diligently running scripts/verify-action-pins.sh for each dependency update. I can have a PR up for Dependabot triage within 48 hours and ongoing rule reviews as needed. I've previously managed Python automation projects that involved setting up and maintaining CI scripts, so this aligns well with my experience.