Files
OmniRoute/docs/security/meta.json
Diego Rodrigues de Sa e Souza c73e274dd0 security(rail): local-only route sweep, public-creds structural guard, LTS security baseline and support window (rail 3.8.57) (#16209)
* test(security): sweep spawn-capable routes for LOCAL_ONLY classification

Filesystem sweep proving Hard Rules #15/#17 for the LTS: every route.ts under
/api/mcp, /api/cli-tools/runtime, /api/services and the dashboard embed proxy
is LOCAL_ONLY for every write method, the only read exemptions inside those
roots are the pinned MCP audit routes, every one is classified MANAGEMENT (the
class whose policy runs the loopback gate), the manage-scope carve-out cannot
cover the spawning roots, and any src/app/api file (helpers included) that
spawns directly belongs to a LOCAL_ONLY route. Validated by mutation: dropping
the /api/services/ prefix, a new GET exemption, or a fork() helper module each
turn it red, while check:route-guard-membership stays green on the helper case.

* test(security): value-based guard against raw public credential literals

Structural layer for Hard Rule #11 next to the key-based check:public-creds
gate: matches the credential formats themselves (Google OAuth client id,
GOCSPX- secret, AIza key, GitHub OAuth app id, non-empty client_secret
literal) anywhere in src/lib/oauth, open-sse and src/shared/constants, with
resolvePublicCred() lines as the only sanctioned form, and pins that
publicCreds.ts keeps its embedded defaults as masked byte arrays. Fixtures are
built at runtime so the test file itself carries no scanner-matching literal.
Validated by mutation: a bare const client id in src/shared/constants and an
AIza key in an open-sse URL turn it red while the gate stays green.

* docs(security): LTS support window and measured LTS security baseline

SECURITY.md gains the LTS support window section for v3.9.x (stable/v3
receives fixes, security patches and provider updates; reporting goes through
the same private advisory channel) with the window duration explicitly marked
as a pending owner decision (T-GAP-3), and lists 3.9.x as the planned LTS line
in Supported Versions.

docs/security/LTS_SECURITY_BASELINE.md records the measured 2026-10-10 state
with the command behind every number: npm audit, open code-scanning /
Dependabot / secret-scanning alerts, the five security workflows, OpenSSF
Scorecard, and the npm publish provenance path (OIDC trusted publishing +
SLSA provenance on 3.8.49-3.8.51) plus the gaps left for the rehearsal.
2026-10-10 09:57:37 -03:00

18 lines
303 B
JSON

{
"title": "Security",
"pages": [
"GUARDRAILS",
"ERROR_SANITIZATION",
"INFERENCE_AUTH_POSTURE",
"ROUTE_GUARD_TIERS",
"BAN_DETECTION",
"AGENTROUTER_WAF",
"CORS",
"EGRESS_POLICY",
"SUPPLY_CHAIN",
"LTS_SECURITY_BASELINE",
"COMPLIANCE",
"CLI_TOKEN"
]
}