Repository navigation
v0.2.0
Added
-
Pépin is bilingual, and detects the language. Reports, verdict, help,
errors and the parsable formats (json,sarif,oscal,assessment) come
out in French or in English. Resolution order:
--lang=fr|en→PEPIN_LANG→LC_ALL→LANG→ fallbacken; the first
non-empty source decides, and an unknown locale falls back to English without
an error. Until now the skeleton was English and the content French, so a
reader got a report in two languages within one sentence.
French remains the reference language of the normative content: the reference
and the rules are written in French first, and where a legal reading is at
stake it is the French wording of a control that governs. -
The project has a mark.
docs/assets/brand/holds the icon and the
lockups in SVG and PNG, light, dark and monochrome, with the generators that
produce them (scripts/generer-marque.py,scripts/generer-png-marque.py)
and the usage rules indocs/brand.md. Both READMEs open on it.
Changed
-
A finding's prose changes with the language, its keys do not. Codes
(CLD-*), check identifiers, severities, statuses, subjects and exit codes are
identical in both languages; titles, messages, remediations and evidence are
translated. A pipeline that diffs report text between runs should pin
PEPIN_LANG. A pipeline keyed on codes and statuses is unaffected. -
A sealed bundle carries the language of the scan that produced it.
verify --re-derivereplays the rules in both languages and accepts either
match, so verifying a French bundle from an English shell is not reported as a
falsification. Note that the bundle digest does depend on the language, since
the assessment's prose is part of what is sealed. -
CLI surface v1 → v2: the persistent
--langflag is added. Pure addition —
no verb, no other flag and no exit code moved. -
docs/doc-cache-brief.mdmoves out of the product documentation. It was a
maintainer's memo addressing a machine ("already downloaded on this machine"),
describing a cache a clone cannot have, linked from nowhere, and carrying six
absolute paths into a home directory. What it held that was worth keeping
moves toreferences/docs/README.md, beside thesources.yamlit describes --
including the trap that matters most: the documentation is not the contract.
Fixed
-
The published action installs again. The provenance check added in 0.1.0
calledgh attestation verifywithout a token;ghrefuses to run in a
workflow withoutGH_TOKEN, so the installer treated every binary as
unverifiable and refused it -- for every consumer, on both 0.1.0 and 0.1.1.
The action now suppliesgithub.tokenitself: nobody should have to wire up a
token to install a binary.The gap that let it ship is worth naming. The pull-request job served
install.shover a loopback with the attestation check skipped, so the public
path was never exercised until the post-publication job ran -- after the tag
existed. A job now calls the action against an already-published version on
every pull request.