oscerd opened a new issue, #2834: URL: https://github.com/apache/camel-kamelets/issues/2834
### Background `apache/camel` ships a documented Security Model (`docs/user-manual/.../security-model.adoc`), a root `SECURITY.md` pointer, and an `AGENTS.md` with a Security Model section. The Kamelet Catalog — an Apache Camel sub-project — has none of these, even though a Kamelet is PMC-authored route code with its own trust nuances (the catalog, not the end user, authors the trusted template; the Kamelet runtime lives in `apache/camel`, not here). ### Proposal Add, mirroring the `apache/camel` house style: - `docs/modules/ROOT/pages/security-model.adoc` — a security model that **specialises** the Camel Security Model for Kamelets: trust roles, component families (catalog YAML vs. `camel-kamelets-catalog`/`-crds`/maven-plugin vs. the runtime that lives in `apache/camel`), in/out-of-scope vulnerability classes, false-friend properties, downstream responsibilities, and a closed set of triage dispositions. - `SECURITY.md` (root) — reporting pointer to the Apache Camel ASF process. - `AGENTS.md` (+ `CLAUDE.md` symlink) — AI agent guidelines with the Kamelet-specific Security Model section, matching `apache/camel`. ### Notes - No code changes; documentation only. `nav.adoc` is auto-generated, so the page is reached via the `SECURITY.md` / `AGENTS.md` xrefs. - Reporting stays the existing Camel process (`[email protected]`); this only documents scope. --- _Filed by Claude Code on behalf of Andrea Cosentino (AI-assisted)._ -- 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]
