potiuk opened a new pull request, #1: URL: https://github.com/apache/airflow-steward/pull/1
## Summary Follow-up sanitization pass on the framework, replacing literal Airflow URLs and ASF-domain strings with the framework's placeholder convention. Remaining "Apache Airflow" references are in legitimate `(example: …)` parentheticals, placeholder-convention tables, and the vulnogram SKILL.md documenting the airflow-specific reference implementation — all within the "Airflow as example in comments" rule. ## What's substituted | Literal | Placeholder | |---|---| | `airflow.apache.org/docs/.../security_model.html` | `<security-model-url>` | | `https://airflow.apache.org/` (project website) | `<project-website>/` | | `security.airflow.apache.org` (security-list domain) | `<security-list-domain>` | | `domain: "airflow.apache.org"` (in ponymail/gmail code) | `domain: "<project-domain>"` | | `` `Apache Airflow:` `` (literal title prefix) | `` `<vendor>: <product>:` (e.g. `Apache Airflow:`) `` | ## Files touched 13 files: 5 skills (`allocate-cve`, `import-security-issue`, `import-security-issue-from-pr`, `invalidate-security-issue`, `sync-security-issue`), 6 tool docs (`tools/{ponymail,gmail,vulnogram}/*.md`), `README.md`, and `CONTRIBUTING.md`. ## Test plan - [x] Re-grep across the framework: count of literal `Apache Airflow` / `airflow.apache.org` / `apache/airflow` / `airflow-s/airflow-s` mentions dropped from ~50 to ~36. - [x] Remaining mentions reviewed and confirmed to fall under `(example: …)` parentheticals or placeholder tables. - [ ] Future: refactor `tools/vulnogram/generate-cve-json/` Python implementation to be project-agnostic (currently airflow-specific defaults; the SKILL.md still describes airflow defaults). Once refactored, the framework can ship the implementation, and the SKILL.md can drop the Airflow-specific examples. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
