ci: pilot Psalm security scan, release-please, and PR title lint (#6)

Pilot of the CI tooling discussed for the ontology-provider modules, on
this repo first since it's under active review (see #5).

## What this adds
- **`security-scan.yml`** — runs Psalm's taint analysis
(`--taint-analysis`) on every PR, scoped to mirror the REDCap
consortium's stated security-scan categories (SQL, XSS, cookies,
headers, path traversal, shell, LDAP, curl/SSRF) rather than general
code quality. Findings are also uploaded as SARIF to the Security tab
via `github/codeql-action/upload-sarif`, making them eligible for
Copilot Autofix assignment.
- **`stubs/redcap-em-framework.phpstub`** — minimal method/function
*signatures* (no implementation) for the EM framework surface this
module calls, with `@psalm-taint-sink`/`@psalm-taint-escape`
annotations, so Psalm can do useful taint tracking without needing
REDCap core itself in a public CI runner. Sourced from REDCap's
published EM Framework docs, not REDCap source.
- **`release-please.yml`** — dormant until this branch reaches `main`
(it only triggers on pushes there). Uses `release-type: simple` since
`config.json` has no version field to bump; release-please owns its own
manifest.
- **`pr-title-lint.yml`** — enforces Conventional Commits on PR titles
via `pull_request_target` (safe here — only reads the title, never
checks out fork code), so release-please has something reliable to
parse.
- **`.github/dependabot.yml`** — weekly version-update PRs for
`composer` (Psalm itself) and `github-actions` (the pinned action
versions here).

## Verified before opening this PR
- Ran Psalm against the actual module code (clean) and against a
deliberately tainted throwaway file (correctly flagged `TaintedSql` via
the stubbed `query()` sink and `TaintedHtml`/`TaintedTextWithQuotes` via
`echo`), to confirm the scan detects real taint rather than silently
passing everything.
- Confirmed `--report=psalm-results.sarif` produces valid SARIF (schema
2.1.0) alongside the normal console output, not instead of it.

## Known limitation
Psalm only analyzes PHP. The module's actual JS lives embedded in PHP
heredoc strings, which no mainstream JS static analyzer (ESLint, CodeQL)
can see — that's a separate piece of follow-up work (extracting embedded
`<script>` blocks into real `.js` files), deliberately not part of this
PR.

## Still open
- Repo merge-strategy restriction to squash-only (needed for
release-please to read a clean one-commit-per-PR history) — pending, not
part of this PR.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Author: dconlan

.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/pr-title-lint.yml

@@ -0,0 +1,19 @@
+name: PR title lint
+
+# pull_request_target (not pull_request) so this also runs for PRs from forks -
+# safe here since the action only reads the PR title, it never checks out or
+# executes the fork's code.
+on:
+  pull_request_target:
+    types: [opened, edited, synchronize, reopened]
+
+permissions:
+  pull-requests: read
+
+jobs:
+  main:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release-please.yml

@@ -0,0 +1,17 @@
+name: release-please
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: googleapis/release-please-action@v4
+        with:
+          release-type: simple

.github/workflows/security-scan.yml

@@ -0,0 +1,46 @@
+name: security-scan
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+  security-events: write
+
+jobs:
+  psalm:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: shivammathur/setup-php@v2
+        with:
+          php-version: '8.4'
+          tools: composer
+
+      - run: composer install --no-interaction --no-progress
+
+      # continue-on-error so a failing scan doesn't skip the SARIF upload below -
+      # findings should reach the Security tab even when they fail the job.
+      - name: Run Psalm taint analysis
+        id: psalm
+        run: vendor/bin/psalm --taint-analysis --no-progress --report=psalm-results.sarif
+        continue-on-error: true
+
+      # continue-on-error too: GITHUB_TOKEN is forced read-only on pull_request
+      # runs triggered from forks, regardless of the security-events: write
+      # permission declared above, so this step fails on every fork PR
+      # (this repo has external contributors - see PR #5) for a reason
+      # unrelated to Psalm's actual findings. Without this, that failure
+      # would be indistinguishable from a real security finding.
+      - name: Upload results to code scanning
+        uses: github/codeql-action/upload-sarif@v3
+        with:
+          sarif_file: psalm-results.sarif
+        continue-on-error: true
+
+      - name: Fail the job if Psalm found issues
+        if: steps.psalm.outcome == 'failure'
+        run: exit 1

.gitignore

@@ -2,3 +2,4 @@
 .idea
 .project
 .settings
+vendor

composer.json

@@ -0,0 +1,8 @@
+{
+    "name": "aehrc/redcap-fhir-ontology-provider",
+    "description": "REDCap external module providing FHIR-based ontology autocomplete",
+    "type": "project",
+    "require-dev": {
+        "vimeo/psalm": "^6.16"
+    }
+}