Roadmap health #209

This issue is rewritten every night by the roadmap sweep. It lists what needs attention. Fix what it lists in GitHub, and the next sweep clears the line.

Written 2026-11-01T04:17:46Z, run 41272524066, rules 2026-10-31.1.

Ready to publish

Every issue is done and its work is on main. A project lead closes the milestone.

None.

Closed with open work

Closed milestones that still hold remaining issues.

None.

Closed with open work and nothing done

Closed milestones with no done issues but remaining ones. They show as withdrawn. Reopen any closed by mistake.

None.

Target passed

Open milestones past their committed date or quarter.

None.

Untriaged in a milestone

Open issues in a milestone with no acceptance decision.

None.

Milestoned against a triage decision

The event job declined these because of a standing triage label.

• [RefImpl] Host-side trace follow-ups that wait on PR #229 #285

Unverified closes

Closed as completed, but the data does not show delivery. Each line gives its milestone, its reason code, and the one remedy for that code.

None.

In focus without a milestone

Open in-focus issues not yet placed on the roadmap.

• [Docs] OCSF examples in acs.md and implementation_examples.md contradict the normative mapping #234

Accepted without a milestone

Open accepted issues not yet placed on the roadmap.

• [Docs] OCSF examples in acs.md and implementation_examples.md contradict the normative mapping #234

Accepted by milestone this week

Issues the bot accepted in the last eight days, with who set the milestone.

None.

Unknown close reasons

Closed with a reason this version does not know.

None.

Off-quarter dates

Milestones whose due date is not the last day of a quarter.

None.

Missing description lines

Open milestones without a valid Type line, which the OWASP report needs.

None.

Promotion

Work on integration that main lacks. A project lead opens and merges the promotion.

None.

Bypasses

Merges into integration or main in the last seven days with no approval that could satisfy the ruleset, and direct pushes. Admins can bypass the rulesets, so this is where a bypass shows.

Merged without a qualifying approval in the last seven days: 33.

• Prepare the move of the site to owaspacs.org #416 into integration changed a roster file or roadmap trust code without a qualifying approval.
• State a first-response aim and say triage happens as issues come in #409 into integration changed a roster file or roadmap trust code without a qualifying approval.
• Remove three inert owners from CODEOWNERS #414 into integration changed a roster file or roadmap trust code without a qualifying approval.
• Read the workstream table through one parser, so the landing page drops a commented-out row #411 into integration changed a roster file or roadmap trust code without a qualifying approval.
• Read GH-N as an issue reference in closing_choice #410 into integration changed a roster file or roadmap trust code without a qualifying approval.
• Show one navigation pane on the landing page and the docs #366 into integration changed a roster file or roadmap trust code without a qualifying approval.
• Promote integration to main #424 into main changed a roster file or roadmap trust code without a qualifying approval.
• Promote integration to main #422 into main changed a roster file or roadmap trust code without a qualifying approval.
• Promote integration to main #419 into main changed a roster file or roadmap trust code without a qualifying approval.

Switches

The current value of each roadmap variable, flagged when it is neither true nor false.

• ROADMAP_REFRESH_ENABLED is true
• ROADMAP_RENDER_ENABLED is true
• ROADMAP_SYNC_ENABLED is true