Security: Trivy is a baseline not a gate, and the backend image ships no pip
The Trivy jobs run with --exit-code 0, so a green Trivy check is not evidence of
a clean image -- the findings go to the Security tab instead. Read it after the
final push, not before.
The backend image now uninstalls pip after the application is installed: pip is
not needed at runtime and its vendored msgpack/setuptools were the only source
of HIGH findings against the image. python -m ensurepip restores it in a running
container.
Development/Security: dependency ceilings, the real merge guarantee, and the CodeQL suite name
Development: document the two dependencies deliberately held below their newest
release -- the redis Python client at 5.x because arq pins redis<6, and
typescript below 6.1 because no published typescript-eslint declares support for
TypeScript >=6.1. Both produce a red CI rather than a working upgrade.
Development: the CI & contribution section claimed a pull request must be
up-to-date with main before merging. The ruleset does not require that. Replace
it with what actually holds: a pull_request run tests head merged into the base
tip at the time it runs, so a green check can be stale by the time the merge
happens; and on Dependabot pull requests the three required CodeQL Analyze
contexts never run, so those merges pass through the admin ruleset bypass.
Security: the scan table named the CodeQL query suite "security-and-quality".
Default setup does not offer that suite -- this repository is on "extended",
which resolves to security-extended, confirmed in the config API and in every
analysis's SARIF codeqlConfigSummary.
Security: correct the CodeQL claim; document outbound device TLS
Security.md asserted there is no CodeQL workflow in the repository. CodeQL is
in fact active through GitHub default setup (security-and-quality suite over
Python, JS/TS and Actions), which is precisely why no codeql.yml exists — the
absent file had been read as an absent scanner. Add it to the scan table and
record the Dependabot-PR consequence.
Also document outbound TLS to managed firewalls, which the Transport security
section did not cover: the three per-device trust modes, the fingerprint pin as
the compensating control when verification is off, and the honest gap that an
already-onboarded device cannot have those settings changed from the console.
Troubleshooting now points at the actual field instead of naming the option.
Security: document remember-this-device (trusted devices), v0.21.0
docs(wiki): WebAuthn passkeys as a second MFA factor (v0.20.0)
Log-Lake: CRL hard-revocation (receiver-enforced) + verified HA node-loss; Security: least-privilege syslog CA key
docs: audit log viewer (v0.10.0) + per-tenant retention (v0.11.0)
Audit section in Security (viewer + CI guard + non-RLS code-gate); retention knobs
in Configuration; per-tenant indices + worker-owned retention in Log-Lake; the
report<->retention guard in Reporting; Home capability rows.
docs: Security/Perimeter feature + tunables + refreshed screenshots; perimeter report sections toggled with the others (not per-device)
docs: add UI screenshots to key wiki pages
Embed product screenshots (referenced from the main repo's docs/ui via raw
GitHub URLs) on Home, Architecture, Configuration-Editor, Reporting, Log-Lake,
and Security.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs: comprehensive OPNGMS wiki (install, architecture, config, editor, log lake, security, reporting, ops)
Add the full operator + contributor manual as 12 wiki pages, every claim
grounded in the repository:
- Home / _Sidebar — overview and persistent navigation
- Installation — prerequisites, four TLS models, pull & start, first run
- Architecture — component diagram, services, data flows, RLS multi-tenancy
- Configuration — complete environment-variable reference
- Upgrading — pull+up flow, version pinning, backups, MASTER_KEY rotation
- Configuration-Editor — the version-aware editor & catalog pipeline (3a/3b
built; 3c diff/config.xml-map fenced as planned/not-built)
- Log-Lake — the optional mTLS syslog to OpenSearch lake
- Reporting — SMTP delivery, per-tenant settings, schedules
- Security — RLS, encrypted-at-rest secrets, MFA, CI scans, hardening
- Troubleshooting — grouped symptom to cause to fix
- Development — local dev, tests, CI, contribution flow
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>