Repository navigation
Security
How to report a vulnerability, and how security is engineered into the platform.
Canonical source: SECURITY.md.
- Email
security at yosemitecrew.comwith a description and reproduction steps. - You'll get a response within one business day.
- Please keep the issue confidential until users have had reasonable time to patch, and don't exploit it.
- There's no formal bug-bounty program yet (early-stage project), but reports are handled confidentially, contributors are credited if they wish, and Yosemite Crew commits not to pursue legal action for good-faith, non-exploitative research.
Do not open a public issue for a vulnerability — use the email process above.
Security is designed in at several layers, documented across this wiki:
- No financial custody. The platform is never the merchant of record and never holds clinic funds (Payments Architecture / ADR-0002).
- Provider-neutral auth with self-hosted identity (Authentication and Identity / ADR-0003).
- Org-scoped access control — cross-tenant access is a bug class, not a feature (Multi-Tenancy and RBAC).
- AI agent least privilege — the developer AI editing agent is draft-only, config-scoped, human-promoted, and designed assuming the model is compromised (ADR-0005).
- Data residency posture is explicit and contractual (ADR-0004).
- Federation trust boundary - clinic-to-clinic ActivityPub traffic is HTTP-signature verified, gated to verified organisations, and outbound fetches carry SSRF / DNS-rebinding defences (ActivityPub Federation).
-
Secrets never committed — Secretlint + staged-secret scanner (and gitleaks if installed) on
pre-commit; Gitleaks in CI. Rotate immediately on any suspected leak. - SAST + secrets via Aikido before every push / PR (Code Quality Gates).
- CodeQL and dependency-review run in CI (CI/CD Pipeline).
- Explicit validation at boundaries (Zod on the backend), secure defaults, least privilege.
A small set of standing workflows exists to catch classes of quiet failure early:
-
supply-chain.yml- SBOM, vulnerability (Grype) and license (Grant) scanning of the dependency tree. -
tls-expiry.yml- daily certificate-expiry check on the public hostnames, so a failed renewal is flagged weeks before it bites. -
promotion-guard.ymlandback-merge.yml- branch-integrity enforcement:maintakes changes only fromdev, and anything reachingmainis merged back sodevalways contains it. -
asc-key-check.yml- on-demand check that the App Store Connect API key still authenticates, surfacing a credential problem in seconds instead of after a full release build.
- IDOR / object-authorization fixes are handled as they're found (e.g. mobile task-detail access scoping).
-
Supply-chain security (epic #1721) is delivered: the
supply-chain.ymlworkflow backed byscripts/security/supply-chain.sh, policy files.grype.yaml/.grant.yaml, pinnedpnpm.overridesfor transitive dependencies, and the process docdocs/security/supply-chain.md. - The security-hardening workstream - cross-tenant authorization, RBAC scoping, and CI supply-chain (#1796, remediating the automated-scan findings in #1638) - closed on 2026-07-14. Its successor, the 292-finding triage, landed in PR #1860 (merged 2026-07-18), which hardened cross-tenant authorization and permission checks repo-wide: tenant scope is now derived from the resource being accessed.
- A further backend authorization hardening sweep landed across 2026-08: org scoping derived from the resource on routes that previously trusted caller-supplied ids, cross-tenant binding checks on invoices, bookings, clinical records and uploads (e.g. proving companion ownership before a booking is written, binding an invoice to its Stripe payment intent), unforgeable rate-limit keys, complete user deletion, and clinical-record reads put behind their own permission with an audit trail.
SOC 2 Type 1, ISO 27001:2022, GDPR alignment, and EU accessibility obligations are covered in Compliance and Certifications.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki