Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?

Risks / R10 This newsroom's own agents are steered, leak or mislead / R10-2

R10-2: A vault key or token published

Because every file in the repository is public within minutes of a push to dev, a vault key, access token or passphrase written into the tree would be published, resulting in the evidence or readers' data opened to anyone.

Rating 10 medium · Likelihood 2 Unlikely · Impact 5 Severe · Kind AI and agents · Acceptance not recorded

Basis. Credential shapes and vault files refused by the gate and the release tripwire.

The path

Told innone yetActed on byThe editorThe editordev@php.newsroomdev@php.newsroomConductorConductorCarried byThe newsroom's agents (treater)The newsroom's agent…The editor (owner)The editor (owner)This site's readers (bearer)This site's readers …RiskR10-2 A vault key or token publishedR10-2 A vault key or…Arises fromAgents that read the open web and can publishAgents that read the…Vulnerabilitynone yetFixed bynone yetCodeadmin/build/release.shadmin/build/release.…admin/build/validate.pyadmin/build/validate…admin/build/security_check.pyadmin/build/security….github/workflows/pages.yml.github/workflows/pa…
The risk sits in the middle. To its left, the stories that tell it, the roles and team members that act on it, and every stakeholder that carries part of it. To its right, what it arises from, the vulnerability behind that, the part of the fix that addresses it and the code the fix changed. Every line is an edge in the graph; every node is a link; hover for the full name. Vulnerabilities, stories and team members include those of the risk this one is part of; roles include those of the risks above and beneath it.

Who carries it

One risk, assigned to every stakeholder that carries part of it, with the part each plays.

StakeholderPartWhyIts register
The newsroom's agentstreaterClone outside the repository; never print a secret.4 risks
The editorownerHolds the root key; rotates on exposure.4 risks
This site's readersbearerTheir subscriptions and telemetry are in vaults.3 risks

What it arises from

The evidence

No claim on this site carries this risk: it rests on how this newsroom works, set out on the pages linked below.

Treatments

TreatmentStatusWhere
Credential-shape and vault-file checks in the gate and on the staged diffin placeThe vaults behind this site

The standards that govern it

FrameworkControlWhat it asksFamily
OWASP Top 10sLLM02:2025Sensitive information disclosurePractice and technique
GDPRArt.32Security of processing, including a process for regularly testing and evaluating itLaw and regulation
ISO/IEC 27001A.5.14Information transfer, including under agreed classificationManagement-system standards

The stories that tell it

On this site: The vaults behind this site