Downstream Projects

Every project built from the RHEA template, and how far each has diverged from it. Two things are tracked separately, because they mean different things: whether a project is up to date with the security baseline core defines, and how far its copy of the shared surface has drifted.

Drift is not a grade. Projects own their own code and are free to change it. What matters is the security column.

downstream
Project status
14.0

How to read this

Security is graded by whether the protections core defines are present, not by whether the files match. A project may rewrite its own copy of a sanitizer and remain fully protected; another may be byte-identical on that file yet lack a required CSP directive. Grading by drift conflated freedom to customise with exposure.

Code is how far the shared surface has drifted, and is informational. Most drift found in practice is comment-only — a stale explanation left behind when the code moved on.

Not adopted counts the deliberate divergences recorded for a project: what it does not take from core, and why. These are the difference between “this project is behind” and “this project is deliberately different”. Without them, a well-meaning sync re-breaks things that were fixed on purpose.

Why the security column is not more specific

Naming which control a given production site is missing would publish a targeting aid. The column reports a count and the affected area only.

Maintainers get the specifics by running the generator against one project, which needs code access anyway: python3 scripts/rhea-downstream/generate.py --project OWNER/REPO in eds-site-config.

Keeping this current

The data is a snapshot. It cannot be produced on demand: the scan reads around 1,400 repositories, which needs a personal access token rather than the repo-scoped one available to automation, and a full pass takes about twenty-six minutes.

A scheduled job in eds-site-config regenerates it and publishes straight to the delivery tier, so there is nothing to commit and nothing on this site to update. To regenerate by hand, run python3 scripts/rhea-downstream/generate.py --kv downstream --no-discover there. Dropping --no-discover adds the org-wide check for projects that are not yet registered, at the cost of the full twenty-six minutes.

Past fourteen days the line above escalates to a warning. A stale dashboard is worse than none, because silence reads as no divergence.