VERIFICATION-0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
Security evidence state · Extended localized content for verification and layout resilience
- Verified
- 18
- Violated
- 1
- Unknown
- 3
- Stale
- 2
- N/A
- 4
<forma-security-state-matrix>
Counts security results by explicit state (Verified, Violated, Unknown, Stale, N/A) so no state collapses into another or into a score.
<forma-security-state-matrix>patterns/security-state-matrix.htmlThe security state matrix shows how many invariants or evidence records Tutela places in each state: Verified, Violated, Unknown, Stale and N/A. Each state is a labelled tile with its count as large text, and every state is always shown, including zero, so Unknown and Stale are as visible as Violated. It is a count display, not a score: the tiles are never summed into a percentage or grade. To compare several scopes, repeat the matrix once per scope with the scope named in its heading. Tutela supplies the counts; Forma never computes them.
data-state on each tile carries the machine state name.The smallest correct markup: the canonical pattern from patterns/security-state-matrix.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
<forma-security-state-matrix class="forma-component-tag">
<section class="forma-security-state-matrix" aria-labelledby="security-state-title">
<h2 id="security-state-title">Security evidence state</h2><dl class="forma-security-state-matrix__grid">
<div data-state="verified"><dt>Verified</dt><dd>18</dd></div><div data-state="violated"><dt>Violated</dt><dd>1</dd></div>
<div data-state="unknown"><dt>Unknown</dt><dd>3</dd></div><div data-state="stale"><dt>Stale</dt><dd>2</dd></div><div data-state="na"><dt>N/A</dt><dd>4</dd></div>
</dl></section>
</forma-security-state-matrix>
Click or tap the code once to select all of it, then copy.
Counts for an artifact that has just been assessed. Zero counts are shown rather than omitted, so the large Unknown count is read in context.
<forma-security-state-matrix class="forma-component-tag">
<section class="forma-security-state-matrix" aria-labelledby="security-state-matrix-new-artifact-title">
<h2 id="security-state-matrix-new-artifact-title">Security evidence state for build 7f3c9a2</h2>
<dl class="forma-security-state-matrix__grid">
<div data-state="verified"><dt>Verified</dt><dd>0</dd></div>
<div data-state="violated"><dt>Violated</dt><dd>0</dd></div>
<div data-state="unknown"><dt>Unknown</dt><dd>26</dd></div>
<div data-state="stale"><dt>Stale</dt><dd>0</dd></div>
<div data-state="na"><dt>N/A</dt><dd>2</dd></div>
</dl>
</section>
</forma-security-state-matrix>
Click or tap the code once to select all of it, then copy.
Two scopes compared by repeating the matrix, each with the scope in its heading. The layout never implies that counts from different scopes can be added together.
<forma-security-state-matrix class="forma-component-tag">
<div class="forma-stack">
<section class="forma-security-state-matrix" aria-labelledby="security-state-matrix-per-scope-auth-title">
<h3 id="security-state-matrix-per-scope-auth-title">Authentication boundary</h3>
<dl class="forma-security-state-matrix__grid">
<div data-state="verified"><dt>Verified</dt><dd>9</dd></div>
<div data-state="violated"><dt>Violated</dt><dd>0</dd></div>
<div data-state="unknown"><dt>Unknown</dt><dd>1</dd></div>
<div data-state="stale"><dt>Stale</dt><dd>0</dd></div>
<div data-state="na"><dt>N/A</dt><dd>1</dd></div>
</dl>
</section>
<section class="forma-security-state-matrix" aria-labelledby="security-state-matrix-per-scope-egress-title">
<h3 id="security-state-matrix-per-scope-egress-title">Network egress boundary</h3>
<dl class="forma-security-state-matrix__grid">
<div data-state="verified"><dt>Verified</dt><dd>2</dd></div>
<div data-state="violated"><dt>Violated</dt><dd>1</dd></div>
<div data-state="unknown"><dt>Unknown</dt><dd>2</dd></div>
<div data-state="stale"><dt>Stale</dt><dd>2</dd></div>
<div data-state="na"><dt>N/A</dt><dd>0</dd></div>
</dl>
</section>
</div>
</forma-security-state-matrix>
Click or tap the code once to select all of it, then copy.
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
The five state tiles at phone width.
clamp(1.4rem, 4vw, 2rem)), so they shrink slightly on phones without truncation.<forma-security-state-matrix class="forma-component-tag">
<section class="forma-security-state-matrix" aria-labelledby="security-state-matrix-mobile-title">
<h2 id="security-state-matrix-mobile-title">Security evidence state</h2>
<dl class="forma-security-state-matrix__grid">
<div data-state="verified"><dt>Verified</dt><dd>18</dd></div>
<div data-state="violated"><dt>Violated</dt><dd>1</dd></div>
<div data-state="unknown"><dt>Unknown</dt><dd>3</dd></div>
<div data-state="stale"><dt>Stale</dt><dd>2</dd></div>
<div data-state="na"><dt>N/A</dt><dd>4</dd></div>
</dl>
</section>
</forma-security-state-matrix>
Click or tap the code once to select all of it, then copy.
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-labelledby | section.forma-security-state-matrix | id of the heading | — | Names the region; include the scope or subject in the heading. |
data-state | .forma-security-state-matrix__grid > div | verified | violated | unknown | stale | na | — | Machine state name for the tile. Not styled by Forma CSS; the dt text is the visible label. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-security-state-matrix | Block class | — | Root section: bordered, padded primary surface. |
.forma-security-state-matrix__grid | Element class | — | Description list laid out as an auto-fit grid of tiles at least 7rem wide. Each tile has a 0.25rem top border in the current text color (CanvasText in forced colors) and a secondary surface; dt is a small bold label and dd a large fluid count. |
| Keys | Result |
|---|---|
| — | Not interactive. Link to detailed lists from surrounding content if readers need to drill in. |
| Event | Description |
|---|---|
— | No events. |
Not a form control.
| State | How it is expressed | Presentation |
|---|---|---|
| Verified | tile data-state="verified" | Count of verified results. |
| Violated | tile data-state="violated" | Count of violated results. |
| Unknown | tile data-state="unknown" | Count of results that could not be established; same visual weight as Violated. |
| Stale | tile data-state="stale" | Count of results whose evidence is invalidated. |
| N/A | tile data-state="na" | Count of results not applicable to the scope. |
Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.