Veredictum

Miradi inayofuata mazoea bora hapa chini inaweza kujihakikisha kwa hiari na kuonyesha kuwa wamepata nishani ya mazoea bora ya Open Source Security Foundation (OpenSSF).

Hakuna seti ya mazoea yawezayo kuhakikisha kuwa programu haitakuwa na kasoro au udhaifu; hata mbinu rasmi zinaweza kushindwa ikiwa vipimo au dhana ni sahihi. Wala hakuna seti ya mazoea yawezayo kuhakikisha kuwa mradi utaendelea kuwa na jamii ya maendeleo yenye afya na inayofanya kazi vizuri. Hata hivyo, kufuata mazoea bora kunaweza kusaidia kuboresha matokeo ya miradi. Kwa mfano, baadhi ya mazoea huwezesha ukaguzi wa watu wengi kabla ya kutolewa, ambayo inaweza kusaidia kupata udhaifu wa kiufundi ambao vinginevyo ni vigumu kupata na kusaidia kujenga uaminifu na hamu ya mwingiliano wa kurudia kati ya wasanidi programu kutoka makampuni tofauti. Ili kupata nishani, vigezo vyote vya LAZIMA na LAZIMA WALA USIWAHI lazima vifuatwe, vigezo vyote vya INAPASWA lazima vifuatwe AU visivyo fufufutiliana na thibitisho, na vigezo vyote vya PENDEKEZA lazima vifuatwe AU visivyo fufufutiliana (tunataka vifikiwe angalau). Ikiwa unataka kuingiza maandishi ya thibitisho kama maoni ya jumla, badala ya kuwa maelezo ya busara kwamba hali ni inakubaliwa, anza kifungu cha maandishi na '//' ikifuatiwa na nafasi. Maoni ni karibu kupitia tovuti ya GitHub kama masuala au maombi ya kuvuta Kuna pia orodha ya barua pepe kwa majadiliano ya jumla.

Tunafuraha kutoa habari katika lugha nyingi, hata hivyo, ikiwa kuna mgongano au kutokuwa na usawa kati ya tafsiri, toleo la Kiingereza ni toleo lenye mamlaka.
Ikiwa huu ni mradi wako, tafadhali onyesha hadhi ya nishani yako kwenye ukurasa wa mradi wako! Hadhi ya nishani inaonekana kama hii: Kiwango cha nishani kwa mradi 14252 ni silver Hapa ni jinsi ya kuiweka:
Unaweza kuonyesha hali ya nishani yako kwa kuweka hii katika faili yako ya markdown:
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/14252/badge)](https://www.bestpractices.dev/projects/14252)
au kwa kuweka hii katika HTML yako:
<a href="https://www.bestpractices.dev/projects/14252"><img src="https://www.bestpractices.dev/projects/14252/badge"></a>


Hizi ni vigezo vya kiwango cha Fedha. Unaweza pia kuangalia vigezo vya kiwango cha Kupita au Dhahabu.

Baseline Series: Kiwango cha Msingi 1 Kiwango cha Msingi 2 Kiwango cha Msingi 3

        

 Misingi 17/17 ●

  • Jumla

    Kumbuka kwamba miradi mingine inaweza kutumia jina sawa.

    An independent conformance instrument for openEHR clinical data repositories. A machine-readable catalogue of 1103 spec-cited test cases and 247 operation bindings is driven against a running CDR over its own REST wire; verdicts are a pure function of the party statement, the recordings, the catalogue and the capability matrix, and the emitted record is sealed with a SHA-256 digest manifest and a detached OpenPGP signature so anyone can re-check it. Every expectation cites the released openEHR specification section it enforces, and the specification text is vendored so each citation resolves.

    Tafadhali tumia muundo wa maneno ya leseni ya SPDX; mifano ni pamoja na "Apache-2.0", "BSD-2-Clause", "BSD-3-Clause", "GPL-2.0+", "LGPL-3.0+", "MIT", na "(BSD-2-Clause OR Ruby)". Usitumie alama za nukuu za moja au mbili.
    Ikiwa kuna lugha zaidi ya moja, ziorodhe kama thamani zilizotengwa kwa koma (nafasi ni za hiari) na ziorodhe kuanzia iliyotumiwa zaidi hadi iliyotumiwa kidogo. Ikiwa kuna orodha ndefu, tafadhali orodhesha angalau tatu za kawaida zaidi. Ikiwa hakuna lugha (k.m., huu ni mradi wa nyaraka tu au wa majaribio tu), tumia herufi moja "-". Tafadhali tumia herufi kubwa za kawaida kwa kila lugha, k.m., "JavaScript".
    Common Platform Enumeration (CPE) ni mpango wa kuweka majina yenye muundo kwa mifumo ya teknolojia ya habari, programu, na vifurushi. Inatumika katika mifumo na hifadhidata nyingi wakati wa kuripoti udhaifu.

  • Mahitaji ya awali


    Ya kutosha kwa nishani!

    Mradi LAZIMA ufikie nishani ya kiwango cha kuhitimu. [achieve_passing]

  • Maudhui ya kimsingi ya tovuti ya mradi


    Ya kutosha kwa nishani!

    Habari juu ya jinsi ya kuchangia LAZIMA ijumuishe mahitaji ya michango inayokubalika (k.m., rejea kwa kiwango chochote kinachohitajika cha msimbo). (URL inahitajika) [contribution_requirements]

    CONTRIBUTING.md states the requirements for an acceptable contribution: the gate commands every PR must pass (cargo build/clippy -D warnings/fmt --check/nextest/deny check, plus veredictum validate at zero findings), the hard rules (every expectation cites its specification section; never weaken, skip or delete a test; coverage ratchets up only; a red row is attributed before anything changes; comment form per RFC 505 and RFC 1574), enforced-signed commits, conventional-commit subjects, a same-PR changelog entry, and tests with behaviour changes: https://github.com/rubentalstra/Veredictum/blob/main/CONTRIBUTING.md


  • Usimamizi wa mradi


    Ya kutosha kwa nishani!

    Mradi UNAPASWA kuwa na utaratibu wa kisheria ambapo wasanidi wote wa kiasi kisicho kidogo cha programu ya mradi wanathibitisha kwamba wameruhusiwa kisheria kufanya michango hii. Mbinu ya kawaida na rahisi ya kutekeleza hii ni kwa kutumia Cheti cha Msanidi cha Asili (DCO), ambapo watumiaji huongeza "signed-off-by" katika ahadi zao na mradi unaunganisha kwenye tovuti ya DCO. Hata hivyo, hii YAWEZA kutekelezwa kama Makubaliano ya Leseni ya Mchangiaji (CLA), au utaratibu mwingine wa kisheria. (URL inahitajika) [dco]
    DCO ni utaratibu unaopendekeza kwa sababu ni rahisi kutekeleza, kufuatilia katika msimbo wa chanzo, na git inasaidia moja kwa moja kipengele cha "signed-off" kwa kutumia "commit -s". Ili kuwa na ufanisi zaidi ni bora ikiwa nyaraka za mradi zinaeleza maana ya "signed-off" kwa mradi huo. CLA ni makubaliano ya kisheria yanayofafanua masharti ambayo kazi za kiakili zimetolewa leseni kwa shirika au mradi. Makubaliano ya mgawo wa mchangiaji (CAA) ni makubaliano ya kisheria yanayohamisha haki katika kazi ya kiakili kwa chama kingine; miradi haihitajiki kuwa na CAA, kwa kuwa kuwa na CAA huongeza hatari kwamba wachangiaji watarajiwa hawatachangia, hasa ikiwa mpokeaji ni shirika la faida. Apache Software Foundation CLAs (leseni ya mchangiaji wa mtu binafsi na CLA ya kampuni) ni mifano ya CLA, kwa miradi ambayo inaamua kwamba hatari za aina hizi za CLA kwa mradi ni chini ya manufaa yao.

    Inbound = outbound, by the licence itself rather than by a separate agreement: Apache-2.0 section 5 places every contribution under the same licence unless the contributor explicitly states otherwise, and CONTRIBUTING.md and GOVERNANCE.md § What this project will not do both restate it — there is no CLA and no copyright assignment, contributors keep their copyright, and the licence stays Apache-2.0 for everyone including the maintainer. Authorship is verifiable rather than asserted: every commit in the history is OpenPGP-signed and the main ruleset refuses an unsigned one. There is no DCO sign-off trailer: https://github.com/rubentalstra/Veredictum/blob/main/CONTRIBUTING.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA ufafanue kwa uwazi na kuandika muundo wake wa utawala wa mradi (njia ya kufanya maamuzi, ikiwa ni pamoja na majukumu muhimu). (URL inahitajika) [governance]
    Kunahitaji kuwa na njia fulani iliyowekwa vyema ya kuandikwa ya kufanya maamuzi na kutatua migogoro. Katika miradi midogo, hii inaweza kuwa rahisi kama "mmiliki wa mradi na kiongozi hufanya maamuzi yote ya mwisho". Kuna miundo mbalimbali ya utawala, ikiwa ni pamoja na dictator wa wema na meritocracy rasmi; kwa maelezo zaidi, angalia Miundo ya utawala. Mbinu zote mbili za kati (k.m., mtunzaji mmoja) na zisizo za kati (k.m., watunzaji wa kikundi) zimetumika kwa mafanikio katika miradi. Habari za utawala hazihitajiki kuandika uwezekano wa kuunda uma wa mradi, kwa kuwa hiyo ni iwezekanavyo kila wakati kwa miradi ya FLOSS.

    GOVERNANCE.md documents the model as it actually is: one maintainer with final say, why the released specifications and not the maintainer decide conformance (including the stated conflict of interest with FerroEHR, a CDR this instrument grades), where decisions are recorded, how a change gets in, how someone becomes a maintainer, and the standing refusals: https://github.com/rubentalstra/Veredictum/blob/main/GOVERNANCE.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA upitishe kanuni ya mwenendo na kuiweka mahali pa kawaida. (URL inahitajika) [code_of_conduct]
    Miradi inaweza kuweza kuboresha uadilifu wa jamii yao na kuweka matarajio kuhusu tabia inayokubalika kwa kupitisha kanuni ya mwenendo. Hii inaweza kusaidia kuepuka matatizo kabla hayajatokea na kufanya mradi kuwa mahali pa kukaribishwa zaidi ili kuhimiza michango. Hii inapaswa kuzingatia tu tabia ndani ya jamii/mahali pa kazi pa mradi. Mifano ya kanuni za mwenendo ni kanuni ya mwenendo ya kernel ya Linux, Kanuni ya Mwenendo ya Agano la Mchangiaji, Kanuni ya Mwenendo ya Debian, Kanuni ya Mwenendo ya Ubuntu, Kanuni ya Mwenendo ya Fedora, Kanuni ya Mwenendo ya GNOME, Kanuni ya Mwenendo ya Jamii ya KDE, Kanuni ya Mwenendo ya Jamii ya Python, Mwongozo wa Mwenendo wa Jamii ya Ruby, na Kanuni ya Mwenendo ya Rust.

    Contributor Covenant, in the standard root location, with the enforcement contact and the four-tier enforcement ladder, and linked from CONTRIBUTING.md and GOVERNANCE.md: https://github.com/rubentalstra/Veredictum/blob/main/CODE_OF_CONDUCT.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA ufafanue kwa uwazi na kuandika hadharani majukumu muhimu katika mradi na wajibu wao, ikiwa ni pamoja na kazi zozote ambazo majukumu hayo lazima yafanywe. Lazima iwe wazi ni nani ana jukumu lipi, ingawa hii haiwezi kuandikwa kwa njia ile ile. (URL inahitajika) [roles_responsibilities]
    Nyaraka kwa utawala na majukumu na wajibu zinaweza kuwa mahali pamoja.

    GOVERNANCE.md defines the roles and how a change gets in; MAINTAINERS.md names who holds them (one person, since 2026-08-26) and, identity by identity, what each credential can publish; .github/CODEOWNERS carries the review ownership. The three edits that add a maintainer are named explicitly: https://github.com/rubentalstra/Veredictum/blob/main/MAINTAINERS.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA uweze kuendelea kwa usumbufu mdogo ikiwa mtu yeyote anakufa, anakuwa katika hali ya kudhoofika, au vinginevyo hawezi au hataki kuendelea kusaidia mradi. Hasa, mradi LAZIMA uweze kuunda na kufunga masuala, kukubali mabadiliko yaliyopendekezwa, na kutoa matoleo ya programu, ndani ya wiki moja ya uthibitishaji wa upotevu wa msaada kutoka kwa mtu yeyote mmoja. Hii INAWEZA kufanywa kwa kuhakikisha mtu mwingine ana funguo zozote zinazohitajika, nywila, na haki za kisheria ili kuendelea mradi. Watu binafsi wanaoendesha mradi wa FLOSS WANAWEZA kufanya hii kwa kuweka funguo katika sanduku la kufungia na wosia unaowezesha haki zozote zinazohitajika za kisheria (k.m., kwa majina ya DNS). (URL inahitajika) [access_continuity]

    Honest: this is met, and MAINTAINERS.md § Publishing identities and § If the maintainer is unavailable say so first-hand rather than promising a plan. Every identity that can publish under this name terminates at one person's GitHub account, one person's hardware, or one person's registrar login: the OpenPGP commit- and tag-signing key is not escrowed, the repository is user-owned so GitHub account recovery is the only route, and crates.io and Zenodo both hang off that same account. Nothing already published disappears (immutable releases, an undeletable container digest, a permanent Zenodo DOI, Apache-2.0 plus public history so a fork is a complete continuation) — but nothing new ships, and no one else could create or close issues, accept a change, or cut a release within a week. The trigger is a second maintainer with write access and a second holder wherever an identity permits one: https://github.com/rubentalstra/Veredictum/blob/main/MAINTAINERS.md


    Kwa shida ya kutosha kwa nishani.

    Mradi INAPASWA kuwa na "bus factor" ya 2 au zaidi. (URL inahitajika) [bus_factor]
    "Bus factor" (pia inajulikana kama "truck factor") ni idadi ya chini ya washiriki wa mradi ambao wanapaswa kutoweka ghafla kutoka kwenye mradi ("kupigwa na basi") kabla ya mradi kusimama kwa sababu ya ukosefu wa wafanyakazi wenye elimu au wenye uwezo. Zana ya truck-factor inaweza kukadiria hii kwa miradi kwenye GitHub. Kwa maelezo zaidi, angalia Kutathmini Bus Factor ya Hifadhi za Git na Cosentino et al.

    The bus factor is 1. GET /repos/rubentalstra/Veredictum/collaborators returns one login; one person can accept a pull request and cut a release; no organisation or legal entity stands behind the project. The route to a second maintainer, explicitly including one from a competing implementation, is open and documented in GOVERNANCE.md § Becoming a maintainer: https://github.com/rubentalstra/Veredictum/blob/main/GOVERNANCE.md


  • Nyaraka


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na ramani ya barabara iliyoandikwa inayoeleza kile mradi unakusudia kufanya na kutofanya kwa angalau mwaka unaofuata. (URL inahitajika) [documentation_roadmap]
    Mradi huenda usitimiza ramani ya barabara, na hiyo ni sawa; kusudi la ramani ya barabara ni kusaidia watumiaji na wachangiaji watarajiwa kuelewa mwelekeo unaokusudiwa wa mradi. Haihitaji kuwa na maelezo mengi.

    A public roadmap board now exists and is linked from the README: https://github.com/users/rubentalstra/projects/5 — planned, in progress and shipped, as a view over the issue tracker, with milestones as releases. The prose halves back it: ARCHITECTURE.md § 11 Gap-fill roadmap is the ordered content plan for the catalogue (querying/AQL first, then the maximal-coverage template round-trip, the scenario/lifecycle suites, the performance and volumetrics chapter — each a bounded, assignable chapter task ordered by procurement value), and GOVERNANCE.md § What this project will not do is the explicit will-not-do half: no CLA or copyright assignment, no expectation without a specification citation, no gate weakened to go green, no verdict a reader cannot re-derive, no paid pass and no privileged party.


    Ya kutosha kwa nishani!

    Mradi LAZIMA ujumuishe nyaraka za muundo (pia inajulikana kama muundo wa kiwango cha juu) wa programu inayozalishwa na mradi. Ikiwa mradi hauzalishi programu, chagua "haihusiki" (N/A). (URL inahitajika) [documentation_architecture]
    Muundo wa programu unaeleza miundo ya msingi ya programu, yaani, vipengele vikuu vya programu, uhusiano kati yao, na mali muhimu za vipengele na uhusiano hivi.

    ARCHITECTURE.md is the design record rather than a summary of one: the testable surface and case-core field definitions, the per-operation wire bindings, the outcome taxonomy and ambiguity register, the assertion vocabulary, the verdict computation (§ 8), and the population-anchored performance-class model with its journey decomposition (§ 8.14). The user-facing conformance-method chapter is at https://veredictum.eu/docs/methodology.html : https://github.com/rubentalstra/Veredictum/blob/main/ARCHITECTURE.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA uandike kile mtumiaji anaweza na asiweze kutarajia kwa suala la usalama kutoka kwa programu inayozalishwa na mradi ("mahitaji yake ya usalama"). (URL inahitajika) [documentation_security]
    Haya ni mahitaji ya usalama ambayo programu inakusudiwa kukidhi.

    Two documents, and neither repeats the other. SECURITY.md carries what a user can and cannot expect: the supported version is the most recent release only — no maintenance branch, no LTS line, no backports — stated with its consequence for anyone publishing a conformance record; the private reporting route and the response commitments; safe harbour; § Scope notes on which classes are security-relevant here (credentials for the system under test, verdict integrity, release-artifact integrity) and which deliberately are not; and the standing warning never to point the runner at a live clinical deployment, because it writes into the system it tests. ASSURANCE_CASE.md carries the argument behind those requirements, boundary by boundary: https://github.com/rubentalstra/Veredictum/blob/main/SECURITY.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe mwongozo wa "kuanza haraka" kwa watumiaji wapya kuwasaidia kufanya kitu haraka na programu. (URL inahitajika) [documentation_quick_start]
    Wazo ni kuonyesha watumiaji jinsi ya kuanza na kufanya programu ifanye chochote. Hii ni muhimu sana kwa watumiaji watarajiwa kuanza.

    Two of them. The README § Quick start is four commands from a clone to a rendered verdict (validate, copy a party example, run, verdicts), with a prebuilt-binary path and a cargo install path beside it; the documentation site carries the same as its installation and running chapters: https://github.com/rubentalstra/Veredictum#quick-start


    Ya kutosha kwa nishani!

    Mradi LAZIMA ufanye jitihada ya kuweka nyaraka kulingana na toleo la sasa la matokeo ya mradi (ikiwa ni pamoja na programu inayozalishwa na mradi). Kasoro yoyote inayojulikana ya nyaraka inayofanya isilingane LAZIMA irekebishwe. Ikiwa nyaraka kwa ujumla ni za sasa, lakini kwa makosa inajumuisha baadhi ya maelezo ya zamani ambayo sio ya kweli tena, ichukue tu kama kasoro, kisha ifuatilie na urekebishe kama kawaida. [documentation_current]
    Nyaraka ZINAWEZA kujumuisha habari kuhusu tofauti au mabadiliko kati ya matoleo ya programu na/au kuunganisha kwa matoleo ya zamani ya nyaraka. Kusudi la kigezo hiki ni kwamba jitihada inafanywa ili kuweka nyaraka kulingana, siyo kwamba nyaraka lazima ziwe kamili.

    The docs are machine-held to the code. The Docs workflow gates on mdbook-lint over every chapter and a blocking internal link check (lychee) before the site deploys, scripts/checks/site-counts.sh fails if the counts the site prints disagree with what veredictum validate reports over the catalogue, and CI requires a user-visible change to add its CHANGELOG entry in the same pull request. The published API documentation is generated from the source with missing_docs as a lint, so it cannot drift from the code: https://github.com/rubentalstra/Veredictum/actions/workflows/docs.yml


    Ya kutosha kwa nishani!

    Ukurasa wa mbele wa hifadhi ya mradi na/au tovuti LAZIMA utambulishe na kuunganisha kiungo kwa mafanikio yoyote, ikiwa ni pamoja na nishani hii ya mazoea bora, ndani ya masaa 48 ya kutambua hadharani kwamba ufanikio umepatikana. (URL inahitajika) [documentation_achievements]
    Ufanikio ni seti yoyote ya vigezo vya nje ambavyo mradi umefanya kazi mahususi kukidhi, ikiwa ni pamoja na nishani fulani. Habari hii haihitaji kuwa kwenye ukurasa wa mbele wa tovuti ya mradi. Mradi unaotumia GitHub unaweza kuweka mafanikio kwenye ukurasa wa mbele wa hifadhi kwa kuyaongeza kwenye faili ya README.

    The README's badge rows are live readings, not claims, and they include this badge (project 14252) beside OpenSSF Scorecard, SLSA Build L3, the Zenodo DOI, CI, CodeQL and the four SonarQube Cloud ratings; the comment beneath them says which read below their ceiling today and why, check by check: https://github.com/rubentalstra/Veredictum#readme


  • Ufikiaji na kimataifa


    Kwa shida ya kutosha kwa nishani.

    Mradi (tovuti zote za mradi na matokeo ya mradi) INAPASWA kufuata mazoea bora ya ufikiaji ili watu wenye ulemavu bado waweze kushiriki katika mradi na kutumia matokeo ya mradi ambapo ni busara kufanya hivyo. [accessibility_best_practices]
    Kwa programu za wavuti, angalia Miongozo ya Ufikiaji wa Maudhui ya Wavuti (WCAG 2.0) na hati yake inayosaidia Kuelewa WCAG 2.0; angalia pia habari za ufikiaji za W3C. Kwa programu za GUI, zingatia kutumia miongozo ya ufikiaji ya mazingira maalum (kama vile Gnome, KDE, XFCE, Android, iOS, Mac, na Windows). Baadhi ya programu za TUI (k.m., programu za `ncurses`) zinaweza kufanya mambo fulani ili kuzifanya kufikika zaidi (kama mpangilio wa `force-arrow-cursor` wa `alpine`). Programu nyingi za mstari wa amri zinafikika vizuri kama zilivyo. Kigezo hiki mara nyingi ni N/A, k.m., kwa maktaba za programu. Hapa kuna baadhi ya mifano ya hatua za kuchukua au masuala ya kuzingatia:
    • Toa mbadala za maandishi kwa maudhui yoyote yasiyo ya maandishi ili yaweze kubadilishwa kuwa aina nyingine watu wanahitaji, kama vile chapa kubwa, braille, hotuba, alama au lugha rahisi zaidi ( mwongozo wa WCAG 2.0 1.1)
    • Rangi haitumiwi kama njia pekee ya kuona ya kuwasilisha habari, kuashiria kitendo, kuchochea jibu, au kutofautisha kipengele cha kuona. ( mwongozo wa WCAG 2.0 1.4.1)
    • Uwasilishaji wa kuona wa maandishi na picha za maandishi una uwiano wa tofauti wa angalau 4.5:1, isipokuwa kwa maandishi makubwa, maandishi ya bahati mbaya, na nembo ( mwongozo wa WCAG 2.0 1.4.3)
    • Fanya kazi zote zipatikane kutoka kwenye kibodi (mwongozo wa WCAG 2.1)
    • Mradi wa GUI au wa wavuti INAPASWA kupima na angalau kipaza sauti kimoja cha skrini kwenye jukwaa la lengo (k.m., NVDA, Jaws, au WindowEyes kwenye Windows; VoiceOver kwenye Mac & iOS; Orca kwenye Linux/BSD; TalkBack kwenye Android). Programu za TUI ZINAWEZA kufanya kazi kupunguza uchanganyiko wa ziada ili kuzuia usomaji wa ziada na vipaza sauti vya skrini.

    Not evaluated systematically, so not claimed. The console is built with accessibility affordances in place — ARIA landmarks and labels on the primary navigation, breadcrumbs, the dark-mode toggle and the toast dismissal, and the journey tests select on those aria-labels, so they cannot silently disappear — but no WCAG audit, axe run or assistive-technology pass has been done, and the console is still under construction (image tags published before its first release carry the CLI as the payload). The CLI itself is plain text on a terminal. The trigger is an accessibility evaluation of the console once its screens settle.


    Kwa shida ya kutosha kwa nishani.

    Programu iliyozalishwa na mradi INAPASWA kuwa kimataifa ili kuwezesha upatanifu wa lugha wa rahisi kwa utamaduni, eneo, au lugha ya hadhira lengo. Ikiwa kimataifa (i18n) haihusiki (k.m., programu haizalishi maandishi yanayokusudiwa kwa watumiaji wa mwisho na haipangi maandishi yanayosomeka na binadamu), chagua "haihusiki" (N/A). [internationalization]
    Upatanifu wa lugha "unarejelea upatanifu wa bidhaa, programu au maudhui ya hati ili kukidhi lugha, utamaduni na mahitaji mengine ya soko mahususi la lengo (eneo)." Kimataifa ni "muundo na maendeleo ya bidhaa, programu au maudhui ya hati ambayo huwezesha upatanifu wa lugha wa rahisi kwa hadhira lengo zinazotofautiana katika utamaduni, eneo, au lugha." (Ona "Upatanifu wa Lugha dhidi ya Kimataifa" ya W3C.) Programu inakidhi kigezo hiki kwa kuwa kimataifa tu. Hakuna upatanifu wa lugha kwa lugha nyingine mahususi unaohitajika, kwa kuwa mara tu programu imekuwa kimataifa inawezekana kwa wengine kufanya kazi kwenye upatanifu wa lugha.

    Stated honestly rather than claimed or dismissed. The instrument's own machine surface is locale-independent by design (spec-fixed openEHR identifiers, ISO datetimes, integer arithmetic with no clock or locale in the resolvers, locale-independent rendering in the document assets), and clinical content carries its own language codes through the openEHR RM. But the human-readable surface — CLI output, the report and certificate documents, and the console's UI strings — is English-only with no localization mechanism, so a translator has nothing to hook into today. There is no i18n framework and no second locale.


  • Mengine


    Ya kutosha kwa nishani!

    Ikiwa tovuti za mradi (tovuti, hifadhi, na URL za kupakua) zinahifadhi nywila kwa ajili ya uthibitishaji wa watumiaji wa nje, nywila LAZIMA zihifadhiwe kama mificho iliyorudiwa na chumvi kwa-mtumiaji kwa kutumia kanuni ya upanuaji (iliyorudiarudia) wa funguo (k.m., Argon2id, Bcrypt, Scrypt, au PBKDF2). Ikiwa tovuti za mradi hazihifadhi nywila kwa kusudi hili, chagua "haihusiki" (N/A). [sites_password_security]
    Kumbuka kwamba matumizi ya GitHub yanakidhi kigezo hiki. Kigezo hiki kinatumika tu kwa nywila zinazotumika kwa ajili ya uthibitishaji wa watumiaji wa nje kwenye tovuti za mradi (pia inaitwa uthibitishaji wa ndani). Ikiwa tovuti za mradi lazima ziingie kwenye tovuti zingine (pia inaitwa uthibitishaji wa nje), zinaweza kuhitaji kuhifadhi ishara za uidhinishaji kwa kusudi hilo kwa njia tofauti (kwa kuwa kuhifadhi mficho hakuna maana). Hii inatumia kigezo cha crypto_password_storage kwa tovuti za mradi, sawa na sites_https.

    No project site stores passwords for authentication of external users. The repository and the documentation site are GitHub and GitHub Pages, and the web console has no login at all — which is why its publish flag binds it to loopback and exposing it further is explicitly the operator's decision behind their own gate.


 Udhibiti wa Mabadiliko 1/1 ●

  • Matoleo ya awali


    Ya kutosha kwa nishani!

    Mradi LAZIMA utunze matoleo ya zamani yaliyotumika mara nyingi ya bidhaa au kutoa njia ya usasishaji kwa matoleo mapya. Ikiwa njia ya usasishaji ni ngumu, mradi LAZIMA uandike jinsi ya kufanya usasishaji (k.m., violesura vilivyobadilika na hatua zilizoanishwa kwa undani ili kusaidia usasishaji). [maintenance_or_update]

    Actively maintained: four releases in the current cycle (0.0.1-alpha.1 through 0.1.0-alpha.4, the latest on 2026-08-27), a tracker past #100 under continuous triage, Dependabot plus a scheduled latest-deps lane and a weekly published-image scan that files its own tracking issue, and CHANGELOG.md accumulating entries between cuts: https://github.com/rubentalstra/Veredictum/releases


 Kuripoti 3/3 ●

  • Mchakato wa kuripoti hitilafu


    Ya kutosha kwa nishani!

    Mradi LAZIMA utumie kifuatiliaji cha masuala kwa ajili ya kufuatilia masuala ya mtu binafsi. [report_tracker]

    GitHub Issues, with three typed templates (defect, enhancement, task), labels and milestones, used for both defects and enhancement requests: https://github.com/rubentalstra/Veredictum/issues


  • Mchakato wa kuripoti udhaifu


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe sifa kwa waripoti wa ripoti zote za udhaifu zilizotatuliwa katika miezi 12 iliyopita, isipokuwa kwa waripoti wanaoomba kutojulikana. Ikiwa hakuna udhaifu uliotatuliwa katika miezi 12 iliyopita, chagua "haihusiki" (N/A). (URL inahitajika) [vulnerability_report_credit]

    SECURITY.md § Credit: reporters are named in the advisory and the changelog by default, using whatever name and link they give, and declining credit costs nothing and changes nothing about how the report is handled: https://github.com/rubentalstra/Veredictum/blob/main/SECURITY.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na mchakato ulioandikwa kwa ajili ya kujibu ripoti za udhaifu. (URL inahitajika) [vulnerability_response_process]
    Hii ina uhusiano mkubwa na vulnerability_report_process, ambayo inahitaji kuwa kuna njia iliyoandikwa ya kuripoti udhaifu. Pia inahusiana na vulnerability_report_response, ambayo inahitaji majibu kwa ripoti za udhaifu ndani ya kipindi fulani cha muda.

    SECURITY.md § Reporting a vulnerability and § What you can expect: private reporting through GitHub Security Advisories, an acknowledgement within 5 working days with a documented public-escalation fallback if it does not arrive, an assessment with a severity and an intended fix window within 14 calendar days, and a coordinated disclosure date agreed with the reporter rather than imposed. Safe harbour is stated. The commitments are framed as commitments to the reporter, not conditions on them: https://github.com/rubentalstra/Veredictum/blob/main/SECURITY.md


 Ubora 19/19 ●

  • Viwango vya msimbo


    Ya kutosha kwa nishani!

    Mradi LAZIMA utambulishe miongozo mahususi ya mtindo wa kuandika msimbo kwa lugha kuu inazotumia, na uhitaji kwamba michango kwa ujumla ikidhi. (URL inahitajika) [coding_standards]
    Katika hali nyingi hii inafanywa kwa kurejelea baadhi ya miongozo ya mtindo iliyopo, huenda ikiorodhesha tofauti. Miongozo hii ya mtindo inaweza kujumuisha njia za kuboresha usomaji na njia za kupunguza uwezekano wa kasoro (ikiwa ni pamoja na udhaifu). Lugha nyingi za programu zina miongozo moja au zaidi ya mtindo inayotumika sana. Mifano ya miongozo ya mtindo ni pamoja na miongozo ya mtindo ya Google na Viwango vya Kuandika Msimbo wa SEI CERT.

    CONTRIBUTING.md documents the standards and CLAUDE.md carries the full set: rustfmt, clippy at pedantic-deny, the comment form (line comments only, RFC 505 and RFC 1574, with budgets and typed TODO/NOTE conventions), the citation rule for every expectation, and the test discipline. The machine-readable half is in the repository as configuration: rustfmt.toml, clippy.toml and the workspace lint tables in Cargo.toml: https://github.com/rubentalstra/Veredictum/blob/main/CONTRIBUTING.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA utekeleze kiotomatiki mtindo wake wa kuandika msimbo uliochaguliwa ikiwa kuna angalau zana moja ya FLOSS inayoweza kufanya hivyo katika lugha zilizochaguliwa. [coding_standards_enforced]
    Hii INAWEZA kutekelezwa kwa kutumia zana za uchambuzi mkako na/au kwa kulazimisha msimbo kupitia vifaa vya kurekebisha msimbo. Katika hali nyingi usanidi wa zana umejumuishwa katika hifadhi ya mradi (kwa kuwa miradi tofauti inaweza kuchagua usanidi tofauti). Miradi INAWEZA kuruhusu vighairi vya mtindo (na kwa kawaida itaruhusu); ambapo vighairi vinatokea, LAZIMA viwe nadra na viandikwe katika msimbo katika maeneo yao, ili vighairi hivi viweze kukaguliwa na ili zana ziweze kuzishughulikia kiotomatiki baadaye. Mifano ya zana kama hizo ni pamoja na ESLint (JavaScript), Rubocop (Ruby), na devtools check (R).

    Enforced on every pull request and push, not advisory: cargo fmt --all --check, cargo clippy --locked --workspace --all-targets -- -D warnings (plus the console's ssr and wasm hydrate targets), scripts/checks/comment-style.sh over the whole tree, changelog-structure and same-PR changelog-entry guards, a REUSE lint, an image-label guard, a VEX-advisory guard, zizmor and actionlint over the workflows and hadolint over the Dockerfile — all behind one required conclusion check, with a guard that fails if any job is left out of it: https://github.com/rubentalstra/Veredictum/actions/workflows/ci.yml


  • Mfumo wa ujenzi unaofanya kazi


    Ya kutosha kwa nishani!

    Mifumo ya kujenga kwa binari za asili LAZIMA iheshimu vigezo (vya mazingira) vya mkusanyaji na vya kiunganishi vilivyopitishwa kwao (k.m., CC, CFLAGS, CXX, CXXFLAGS, na LDFLAGS) na kuvipitisha kwenye viito vya mkusanyaji na vya kiunganishi. Mfumo wa kujenga UNAWEZA kuvipanua na bendera za ziada; LAZIMA USIBADILISHE thamani zilizotolewa na zake mwenyewe. Ikiwa hakuna binari za asili zinazozalishwa, chagua "haihusiki" (N/A). [build_standard_variables]
    Inapaswa kuwa rahisi kuwezesha vipengele maalum vya kujenga kama Address Sanitizer (ASAN), au kutii mazoea bora ya ugumu wa usambazaji (k.m., kwa kuwezesha kwa urahisi bendera za mkusanyaji kufanya hivyo).

    The build is cargo end to end, with no bespoke wrapper to swallow anything: it honours the standard cargo and rustc environment conventions (RUSTFLAGS, CARGO_*, profile overrides in Cargo.toml), and native dependencies built through the cc crate honour CC and CFLAGS in the usual way. Nothing in the repository replaces a passed-in flag set.


    Ya kutosha kwa nishani!

    Mfumo wa kujenga na usakinishaji UNAPASWA kuhifadhi taarifa za utatuzi ikiwa zimeombwa katika bendera husika (k.m., "install -s" haitumiwa). Ikiwa hakuna mfumo wa kujenga au usakinishaji (k.m., maktaba za kawaida za JavaScript), chagua "haihusiki" (N/A). [build_preserve_debug]
    K.m., kuweka CFLAGS (C) au CXXFLAGS (C++) inapaswa kuunda taarifa husika za utatuzi ikiwa lugha hizo zinatumika, na hazipaswi kuondolewa wakati wa usakinishaji. Taarifa za utatuzi zinahitajika kwa msaada na uchambuzi, na pia ni muhimu kwa kupima uwepo wa vipengele vya ugumu katika binari zilizokusanywa.

    Deliberate, and commented as such in Cargo.toml: the release profile keeps debug = "line-tables-only" so a production panic names its file and line, and strip stays at its default of none because stripping symbols makes traces incomprehensible. overflow-checks = true is kept on in release for the same reason. Nothing strips by default: https://github.com/rubentalstra/Veredictum/blob/main/Cargo.toml


    Ya kutosha kwa nishani!

    Mfumo wa kujenga kwa programu iliyozalishwa na mradi LAZIMA USIJENGA kwa njia ya kujirudia saraka ndogo ikiwa kuna utegemezi wa kukatana katika saraka ndogo. Ikiwa hakuna mfumo wa kujenga au usakinishaji (k.m., maktaba za kawaida za JavaScript), chagua "haihusiki" (N/A). [build_non_recursive]
    Taarifa ya utegemezi wa ndani ya mfumo wa kujenga wa mradi inahitaji kuwa sahihi, vinginevyo, mabadiliko ya mradi huenda yasijenge vizuri. Mijengo isiyo sahihi inaweza kusababisha kasoro (ikiwa ni pamoja na udhaifu). Kosa la kawaida katika mifumo mikubwa ya kujenga ni kutumia "ujenzi wa kujirudia" au "make ya kujirudia", yaani, mlingano wa saraka ndogo zinazojumuisha faili za chanzo, ambapo kila saraka ndogo inajengwa kwa uhuru. Isipokuwa kila saraka ndogo ni huru kabisa, hii ni kosa, kwa sababu taarifa ya utegemezi si sahihi.

    One cargo workspace with one dependency graph, which cargo builds as a single DAG. There is no recursive make and no per-directory build.


    Ya kutosha kwa nishani!

    Mradi LAZIMA uweze kurudia mchakato wa kuzalisha taarifa kutoka faili za chanzo na kupata matokeo sawa ya biti-kwa-biti. Ikiwa hakuna ujenzi unaofanyika (k.m., lugha za uandishi ambapo msimbo wa chanzo unatumika moja kwa moja badala ya kukusanywa), chagua "haihusiki" (N/A). [build_repeatable]
    Watumiaji wa GCC na clang wanaweza kupata chaguo la -frandom-seed kuwa na manufaa; katika hali fulani, hii inaweza kutatuliwa kwa kulazimisha aina fulani ya mpangilio. Mapendekezo zaidi yanaweza kupatikana kwenye tovuti ya ujenzi unaorudiwa.

    CI builds with --locked against the committed Cargo.lock and a compiler pinned by rust-toolchain.toml; the container build pins its base images by digest (the builder and gcr.io/distroless/cc-debian13:nonroot both by sha256) and a release step checks that the container, rust-toolchain.toml and the Dockerfile agree on the toolchain; release binaries build inside reusable workflows per GitHub's SLSA Build L3 construction and each carries a signed provenance attestation on its digest. A rebuild resolves identical inputs.


  • Mfumo wa usakinishaji


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe njia ya kusakinisha na kuondoa kwa urahisi programu iliyozalishwa na mradi kwa kutumia mkataba unaotumika sana. [installation_common]
    Mifano ni pamoja na kutumia meneja wa kifurushi (kwa mfumo au kiwango cha lugha), "make install/uninstall" (inasaidia DESTDIR), chombo katika muundo wa kawaida, au picha ya mashine pepe katika muundo wa kawaida. Mchakato wa usakinishaji na uondoaji (k.m., kifurushi chake) UNAWEZA kutekelezwa na mtu wa tatu mradi tu ni FLOSS.

    Three install paths, all published: prebuilt x86_64 and aarch64 Linux binaries attached to every release with a sha256sum, a CycloneDX SBOM and a Sigstore bundle; a multi-architecture container image on GHCR (ghcr.io/rubentalstra/veredictum); and the crate on crates.io (cargo install veredictum). The installation chapter carries the commands, including the gh attestation verify invocation: https://veredictum.eu/docs/installation.html


    Ya kutosha kwa nishani!

    Mfumo wa usakinishaji kwa watumiaji wa mwisho LAZIMA uheshimu mkataba wa kawaida kwa kuchagua eneo ambapo vitu vilivyojengwa vinaandikwa kwa wakati wa usakinishaji. Kwa mfano, ikiwa inasakinisha faili kwenye mfumo wa POSIX lazima iheshimu kigezo cha mazingira cha DESTDIR. Ikiwa hakuna mfumo wa usakinishaji au hakuna mkataba wa kawaida, chagua "haihusiki" (N/A). [installation_standard_variables]

    Each path follows its ecosystem's own convention rather than inventing one: cargo install honours CARGO_INSTALL_ROOT and --root for the install location (and cargo uninstall removes it), the release tarballs are relocatable single static binaries extracted wherever the operator chooses, and the container image is addressed by tag or digest with the catalogue and specification roots passed in as mounted paths rather than baked in.


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe njia kwa wasanidi programu wanaoweza kusakinisha haraka matokeo yote ya mradi na mazingira ya msaada yanayohitajika kufanya mabadiliko, ikiwa ni pamoja na majaribio na mazingira ya majaribio. Hii LAZIMA ifanywe kwa kutumia mkataba unaotumika sana. [installation_development_quick]
    Hii INAWEZA kutekelezwa kwa kutumia chombo kilichozalishwa na/au hati za usakinishaji. Utegemezi wa nje kwa kawaida utasakinishwa kwa kuita mfumo na/au meneja wa kifurushi cha lugha, kwa external_dependencies.

    git clone, then cargo run -- validate --root artifacts --specs specs/openehr — the toolchain pins itself from rust-toolchain.toml, so there is nothing to install by hand, and cargo-nextest is the only extra tool and only if you intend to run the suite. CONTRIBUTING.md § Setup and § The gates carry the full sequence: https://github.com/rubentalstra/Veredictum/blob/main/CONTRIBUTING.md


  • Vipengee vilivyotunzwa nje


    Ya kutosha kwa nishani!

    Mradi LAZIMA uorodheshe utegemezi wa nje kwa njia inayoweza kuchakatwa na kompyuta. (URL inahitajika) [external_dependencies]
    Kwa kawaida hii inafanywa kwa kutumia mkataba wa meneja wa kifurushi na/au mfumo wa ujenzi. Kumbuka kwamba hii inasaidia kutekeleza installation_development_quick.

    Computer-processable, at three levels: Cargo.toml declares the direct dependency set with each pin commented for why it is there, the committed Cargo.lock is the exact resolved graph (this repository ships a binary, so it is committed deliberately), and every release attaches a generated SPDX repository SBOM plus a per-artifact CycloneDX SBOM, both Sigstore-attested. REUSE.toml declares the licensing of the vendored trees machine-readably: https://github.com/rubentalstra/Veredictum/blob/main/Cargo.toml


    Ya kutosha kwa nishani!

    Miradi LAZIMA ifuatilie au kwa muda mrefu iangalie utegemezi wao wa nje (ikiwa ni pamoja na nakala za urahisi) kugundua udhaifu unaojulikana, na kurekebisha udhaifu unaoweza kutumiwa vibaya au kuthibitisha kuwa hauwezi kutumiwa vibaya. [dependency_monitoring]
    Hii inaweza kufanywa kwa kutumia zana ya kichambua chanzo / zana ya kuangalia utegemezi / zana ya uchambuzi wa muundo wa programu kama OWASP's Dependency-Check, Sonatype's Nexus Auditor, Synopsys' Black Duck Software Composition Analysis, na Bundler-audit (kwa Ruby). Baadhi ya waendesha kifurushi wanajumuisha taratibu za kufanya hii. Ni kubaliwa ikiwa udhaifu wa vipengele hauwezi kutumiwa vibaya, lakini uchambuzi huu ni mgumu na wakati mwingine ni rahisi kusasisha au kurekebisha sehemu.

    Four lanes, all running: cargo-deny checks the graph against the RustSec advisory database on every pull request and push; Dependabot raises bump PRs with security updates exempt from the configured cooldowns; a scheduled latest-deps workflow detects in-range upstream breakage; and a weekly Trivy scan of the published container image files or updates its own tracking issue. An accepted advisory needs a published OpenVEX justification in security/vex/, which scripts/checks/vex-advisories.sh enforces: https://github.com/rubentalstra/Veredictum/blob/main/deny.toml


    Ya kutosha kwa nishani!

    Mradi LAZIMA au:
    1. fanya iwe rahisi kutambua na kusasisha vipengele vinavyotumiwa tena vilivyotunzwa nje; au
    2. tumia vipengele vya kawaida vinavyotolewa na mfumo au lugha ya programu.
    Kisha, ikiwa udhaifu unapatikana katika kipengele kilichotumiwa tena, itakuwa rahisi kusasisha kipengele hicho. [updateable_reused_components]
    Njia ya kawaida ya kutimiza kigezo hiki ni kutumia mifumo ya usimamizi wa kifurushi ya mfumo na lugha ya programu. Programu nyingi za FLOSS zinasambazwa na "maktaba za urahisi" ambazo ni nakala za ndani za maktaba za kawaida (labda zilizoachana). Kwa yenyewe, hiyo ni sawa. Hata hivyo, ikiwa programu *lazima* itumie nakala hizi za ndani (zilizoachanishwa), basi kusasisha maktaba za "kawaida" kama sasisho la usalama litaacha nakala hizi za ziada bado zenye udhaifu. Hii ni suala hasa kwa mifumo ya wingu; ikiwa mtoa huduma ya wingu anasasisha maktaba zao za "kawaida" lakini programu haitazitumia, basi masasisho hayasaidii kweli. Angalia, k.m., "Chromium: Kwa nini bado haiko katika Fedora kama kifurushi sahihi" na Tom Callaway.

    Every reused component is identified and updateable in place. Rust dependencies are ordinary cargo pins in one workspace table with a committed lockfile — no vendored or forked crate copies exist. The vendored material that does exist is specification text and clinical-model corpora, not code: it is fetched by committed scripts (scripts/vendor/adl2-archetypes.sh, ckm-archetypes.sh, ckm-templates.sh), hand-editing it is a hard rule violation, and the fix for any finding inside it is always the script plus a re-run, so an update is a re-vendor rather than a patch to maintain.


    Ya kutosha kwa nishani!

    Mradi UNAPASWA kuepuka kutumia vitendakazi na API zilizokubaliwa kuwa hazitumiki tena au zilizopitwa na wakati ambapo mbadala wa FLOSS zinapatikana katika seti ya teknolojia inayotumia ("kifurushi cha teknolojia" yake) na kwa wengi wa watumiaji ambao mradi unasaidia (ili watumiaji wawe na ufikiaji wa haraka wa mbadala). [interfaces_current]

    The interface documentation is generated from the same source tree, so it cannot lag the code: the published API documentation is complete (https://docs.rs/veredictum — 100% of the crate documented, with missing_docs as a lint), the JSON Schemas in schemas/ are emitted by the instrument itself and drift-tested against the committed copies, and scripts/checks/site-counts.sh fails if the counts the site states disagree with what validate reports. The command reference chapter documents every subcommand: https://veredictum.eu/docs/commands.html


  • Seti ya majaribio otomatiki


    Ya kutosha kwa nishani!

    Seti ya majaribio ya kiotomatiki LAZIMA itumike kwenye kila ukaguzi wa kuingia kwenye hifadhi iliyoshirikiwa kwa angalau tawi moja. Seti hii ya majaribio LAZIMA itoe ripoti ya mafanikio au kushindwa kwa majaribio. [automated_integration_testing]
    Mahitaji haya yanaweza kuonekana kama sehemu ndogo ya test_continuous_integration, lakini yanazingatia majaribio tu, bila kuhitaji uunganisho wa kuendelea.

    Integration testing runs above the unit level on every pull request and push: cargo nextest run over the whole workspace including the console's SSR suite, veredictum validate over the entire artifact tree (every machine gate over 1103 cases and 247 bindings, zero findings the only passing result), the console journey tests driving the composed console end to end through a browser, and a screenshot guard that fails when a new screen arrives without a capture. An opt-in mode (UI_E2E_REAL_SUTS=1) composes two real CDRs — FerroEHR's published quickstart and EHRbase's official image pairing — and drives the full wizard against each: https://github.com/rubentalstra/Veredictum/actions/workflows/ci.yml


    Ya kutosha kwa nishani!

    Mradi LAZIMA uongeze majaribio ya kurudi nyuma kwa seti ya majaribio ya kiotomatiki kwa angalau 50% ya hitilafu zilizorekebisha ndani ya miezi sita iliyopita. [regression_tests_added50]

    Applied as a rule rather than a habit: CONTRIBUTING.md § Hard rules forbids weakening, skipping or deleting a test or editing one to route around the defect it exposes, and requires a failing test with a TODO naming its issue when the fix is unclear. In practice, the three document-processing defects the fuzzing lane found (literal nesting depth, brace-expansion variants, a citation-resolution stack overflow) each shipped in 0.1.0-alpha.4 with its pinned regression test and its corpus entry kept: https://github.com/rubentalstra/Veredictum/releases


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na seti ya majaribio ya kiotomatiki ya FLOSS inayotoa angalau 80% ya usakinishaji wa taarifa ikiwa kuna angalau zana moja ya FLOSS inayoweza kupima kigezo hiki katika lugha iliyochaguliwa. [test_statement_coverage80]
    Zana nyingi za FLOSS zinapatikana kupima usakinishaji wa majaribio, ikiwa ni pamoja na gcov/lcov, Blanket.js, Istanbul, JCov, na covr (R). Kumbuka kwamba kutimiza kigezo hiki sio uhakika kwamba seti ya majaribio ni ya kina, badala yake, kushindwa kutimiza kigezo hiki ni kiashiria kizito cha seti ya majaribio mbaya.

    Statement coverage is above 80%, measured by cargo-llvm-cov and published continuously by SonarQube Cloud, whose live coverage badge sits in the README badge row: https://sonarcloud.io/component_measures?id=rubentalstra_Veredictum&metric=coverage . The Sonar lane runs the suite under cargo-llvm-cov and imports the merged lcov through sonar.rust.lcov.reportPaths on every pull request and push. The coverage denominator is deliberately narrower than the analysis scope, with each exclusion carrying its reason in sonar-project.properties: the suite does not measure itself, the CLI entry point is argument plumbing over library functions the suite already drives, and the two document-renderer modules are checked by regenerate-and-diff against committed artifacts rather than by a unit assertion.


  • Upimaji wa utendaji mpya


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na sera rasmi iliyoandikwa kwamba kadri utendakazi mkubwa mpya unaongezwa, majaribio ya utendakazi mpya LAZIMA yaongezwe kwenye seti ya majaribio ya kiotomatiki. [test_policy_mandated]

    CONTRIBUTING.md § Pull requests requires tests to accompany behaviour changes and § Hard rules makes the test discipline non-negotiable (never weaken, skip or delete a test; coverage ratchets up only; a case is added, never removed to make a run green). CI refuses a pull request whose suite is not green, behind the single required conclusion check: https://github.com/rubentalstra/Veredictum/blob/main/CONTRIBUTING.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA ujumuishe, katika maelekezo yake yaliyoandikwa kwa mapendekezo ya mabadiliko, sera kwamba majaribio yataongezwa kwa utendakazi mkubwa mpya. [tests_documented_added]
    Hata hivyo, hata sheria isiyo rasmi inakubaliwa mradi majaribio yaongezwe kimakosa.

    Documented in CONTRIBUTING.md as a stated requirement on every contributor, with the full working discipline in CLAUDE.md, and the gate commands listed so a contributor can run exactly what CI will run: https://github.com/rubentalstra/Veredictum/blob/main/CONTRIBUTING.md


  • Bendera za maonyo


    Ya kutosha kwa nishani!

    Miradi LAZIMA iwe na ukali wa juu zaidi na maonyo katika programu iliyozalishwa na mradi, iwezekanavyo vitendo. [warnings_strict]
    Baadhi ya maonyo hayawezi kuwashwa kwa ufanisi kwenye miradi fulani. Kinachohitajika ni ushahidi kwamba mradi unajitahidi kuwasha bendera za onyo ambapo inaweza, ili makosa yagundulika mapema.

    Well beyond the defaults. The workspace lint tables put clippy::all and clippy::pedantic at deny and then name dozens of specific bug-class lints at deny (unwrap_used, expect_used, panic, panic_in_result_fn, indexing_slicing, string_slice, as_conversions, iter_over_hash_type, precedence_bits, unchecked_time_subtraction, allow_attributes_without_reason and more, each with its reason in a comment), and the rust table sets unsafe_code = forbid, non_ascii_idents = forbid, dead_code = deny and let_underscore_drop/lock = deny. CI runs clippy with -D warnings on every target, so any of them fails the build: https://github.com/rubentalstra/Veredictum/blob/main/Cargo.toml


 Usalama 13/13 ●

  • Maarifa ya maendeleo yenye usalama


    Ya kutosha kwa nishani!

    Mradi LAZIMA utekeleze kanuni za muundo salama (kutoka "know_secure_design"), pale inapohusika. Ikiwa mradi hauzalishi programu, chagua "haihusiki" (N/A). [implement_secure_design]
    Kwa mfano, matokeo ya mradi yanapaswa kuwa na mipangilio salama ya kuzuia makosa (maamuzi ya ufikiaji yanapaswa kukataa kwa chaguo-msingi, na usakinishaji wa mradi unapaswa kuwa salama kwa chaguo-msingi). Pia yanapaswa kuwa na kikuu cha kati kikamilifu (kila ufikiaji ambao unaweza kuwekwa kikomo lazima ufanyiwe ukaguzi wa mamlaka na usiweze kuvukwa). Kumbuka kwamba katika hali fulani kanuni zitagombana, na katika hali hiyo chaguo lazima lifanywe (k.m., taratibu nyingi zinaweza kufanya mambo kuwa magumu zaidi, kukiuka "uchumi wa utaratibu" / iweke rahisi).

    The security-relevant design is structural, and ASSURANCE_CASE.md § 2 states the boundaries it rests on (https://github.com/rubentalstra/Veredictum/blob/main/ASSURANCE_CASE.md). A verdict is a pure function of four inputs — the party's statement, the recorded results, the catalogue and the capability matrix — so no server-controlled value can influence its own result, and two independent runners given those inputs must compute identical verdicts; the verification pack exists to check exactly that, so the instrument is not trusted on its own word. The system under test is untrusted by definition: its responses are evidence in a comparison, never instructions, and an expectation is refuted by a better reading of the released specification and by nothing else. Records are sealed with a byte-deterministic SHA-256 digest manifest and a detached RFC 9580 signature that verify-record recomputes — and that plain gpg --verify checks without this binary present — with typed refusals for a manifest entry that would read outside the bundle or silently replace another digest; a performance class is re-derived from the embedded HDR histograms rather than read from a stored summary. Credentials are unrepresentable inline: the IXIT holds environment-variable names and a declared key path, never a secret. Least privilege in the supply chain: ephemeral per-run tokens, crates.io Trusted Publishing with no stored token, and a reviewer-gated environment on the one irreversible leg.


  • Tumia mazoea mazuri ya msingi ya usimbuaji

    Kumbuka kwamba programu fulani haihitaji kutumia taratibu za usimbuaji. Ikiwa mradi wako unazalisha programu ambayo (1) inajumuisha, inaamilisha, au inafanya usimbuaji kuwa hai, na (2) inaweza kutolewa kutoka Marekani (US) kwenda nje ya Marekani au kwa raia asiye wa Marekani, inaweza kuwa ni lazima kisheria kuchukua hatua chache za ziada. Kawaida hii inahusisha tu kutuma barua pepe. Kwa maelezo zaidi, tazama sehemu ya usimbuaji ya Kuelewa Teknolojia ya Chanzo Wazi & Udhibiti wa Usafirishaji wa Marekani.

    Ya kutosha kwa nishani!

    Mifumo ya usalama ya chaguo-msingi ndani ya programu inayozalishwa na mradi LAZIMA ISITEGEMEE algoriti za kriptologia au hali zenye udhaifu mkubwa unaojulikana (k.m., algoriti ya hash ya kriptologia ya SHA-1 au hali ya CBC katika SSH). [crypto_weaknesses]
    Wasiwasi kuhusu hali ya CBC katika SSH unajadiliwa katika CERT: SSH CBC vulnerability.

    No broken or weak primitive is used or accepted: SHA-256 throughout with no truncation, no MD5, no SHA-1, no DES/3DES/RC4, and TLS through rustls, which implements 1.2 and 1.3 only. Signature verification is a real check rather than a formality — verify-record recomputes every digest and verifies the detached signature, so a substituted byte fails.


    Kwa shida ya kutosha kwa nishani.

    Mradi INAPASWA kusaidia algoriti nyingi za kriptologia, ili watumiaji waweze kubadilisha haraka ikiwa moja imevunjwa. Algoriti za kawaida za funguo za simetria ni pamoja na AES, Twofish, na Serpent. Mbadala wa algoriti za hash za kriptologia za kawaida ni pamoja na SHA-2 (ikiwa ni pamoja na SHA-224, SHA-256, SHA-384 NA SHA-512) na SHA-3. [crypto_algorithm_agility]

    Corrected and stated precisely, because it is narrower than a plain no. The record format IS agility-ready: the manifest carries a digest_algorithm identifier naming the algorithm every digest below it was taken with, and verification refuses a manifest signed under the wrong algorithm (app/veredictum/src/record.rs), so adding SHA-512 or SHA-3 is a new enum variant and a match arm rather than a format break. The negotiating layers are agile by construction too — TLS versions and suites are negotiated by rustls, and an OpenPGP signature carries its own hash-algorithm identifier. What is not true today is the criterion's own test: only SHA-256 is implemented, so an operator cannot switch if it breaks. The trigger is a second DigestAlgorithm variant with its selection surface, which belongs on an issue before it is claimed here.


    Ya kutosha kwa nishani!

    Mradi LAZIMA usaidie kuhifadhi vitambulisho vya uthibitishaji (kama vile nywila na ishara za nguvu) na funguo za kibinafsi za kriptologia katika mafaili ambayo yametengwa na habari nyingine (kama vile mafaili ya usanidi, hifadhidata, na kumbukumbu), na kuruhusu watumiaji kusasisha na kubadilisha bila ukusanyaji upya wa msimbo. Ikiwa mradi haufanyi usindikaji wa vitambulisho vya uthibitishaji na funguo za kibinafsi za kriptologia, chagua "haihusiki" (N/A). [crypto_credential_agility]

    Nothing is embedded and nothing needs a recompilation to change. A credential for the system under test never enters the repository at all: the party's IXIT declares only the NAME of the environment variable that carries it, so the secret stays in the operator's environment and out of the catalogue, the records and the logs. The signing key is a file path passed as --sign-key at the moment it is used and is never stored by the tool. The project's own publishing credentials store no secret either — the release lane runs on an ephemeral per-run GITHUB_TOKEN and the crate publishes through crates.io Trusted Publishing (OIDC), as recorded identity by identity in MAINTAINERS.md: https://github.com/rubentalstra/Veredictum/blob/main/MAINTAINERS.md


    Ya kutosha kwa nishani!

    Programu iliyozalishwa na mradi INAPASWA kusaidia itifaki salama kwa mawasiliano yake yote ya mtandao, kama vile SSHv2 au zaidi, TLS1.2 au zaidi (HTTPS), IPsec, SFTP, na SNMPv3. Itifaki zisizo salama kama vile FTP, HTTP, telnet, SSLv3 au mapema zaidi, na SSHv1 ZINAPASWA kuzimwa kwa chaguo-msingi, na kuzimwa tu ikiwa mtumiaji anaisanidi mahususi. Ikiwa programu iliyozalishwa na mradi haiesaidii mawasiliano ya mtandao, chagua "haihusiki" (N/A). [crypto_used_network]

    All network security uses standard published protocols, never bespoke transport cryptography: TLS through rustls on every outbound connection (reqwest is configured with default features off and the rustls feature on, so no platform TLS backend is silently substituted), and JWT (RFC 7519) bearer authentication against a system under test.


    Ya kutosha kwa nishani!

    Programu iliyozalishwa na mradi INAPASWA, ikiwa inasaidia au inatumia TLS, kusaidia angalau toleo la TLS 1.2. Kumbuka kuwa kilichotangulia TLS kiliitwa SSL. Ikiwa programu haitumii TLS, chagua "haihusiki" (N/A). [crypto_tls12]

    The TLS stack is rustls, which implements TLS 1.2 and 1.3 only — an older protocol version is not representable in the library, so there is nothing to disable and no configuration switch that could re-enable one.


    Ya kutosha kwa nishani!

    Programu iliyozalishwa na mradi LAZIMA, ikiwa inasaidia TLS, ifanye uthibitishaji wa cheti cha TLS kwa chaguo-msingi inapotumia TLS, ikiwa ni pamoja na rasilimali ndogo. Ikiwa programu haitumii TLS, chagua "haihusiki" (N/A). [crypto_certificate_verification]
    Kumbuka kuwa uthibitishaji usio sahihi wa cheti cha TLS ni kosa la kawaida. Kwa maelezo zaidi, angalia "The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software" na Martin Georgiev et al. na "Do you trust this application?" na Michael Catanzaro.

    rustls with webpki certificate verification is the default on every outbound TLS connection, and there is no escape hatch: no danger_accept_invalid_certs, no accept_invalid_hostnames and no insecure or no-verify option is exposed anywhere in the configuration surface or the code.


    Ya kutosha kwa nishani!

    Programu iliyozalishwa na mradi LAZIMA, ikiwa inasaidia TLS, ifanye uthibitishaji wa cheti kabla ya kutuma vichwa vya HTTP na habari ya kibinafsi (kama vile vidakuzi salama). Ikiwa programu haitumii TLS, chagua "haihusiki" (N/A). [crypto_verification_private]

    Certificate verification happens before anything private is sent: the client is rustls with webpki verification and no way to switch it off, so the JWT bearer token and any basic-auth credential for the system under test only ever travel over a verified TLS session. Private keys are never transmitted or logged — signing is done locally from a key path the operator passes, only the detached signature leaves the process, and pointer_format is a denied lint so addresses cannot leak into Debug output either.


  • Kutolewa kwa usalama


    Ya kutosha kwa nishani!

    Mradi LAZIMA uweke saini kwa kriptologia matoleo ya matokeo ya mradi yanayokusudiwa kwa matumizi ya kila mahali, na LAZIMA kuwe na mchakato ulioandikwa unaoweleza watumiaji jinsi wanaweza kupata funguo za umma za saini na kuthibitisha saini. Funguo ya kibinafsi kwa saini hizi LAZIMA ISIWE kwenye tovuti zinazosambaza moja kwa moja programu kwa umma. Ikiwa matoleo hayakusudiwa kwa matumizi ya kila mahali, chagua "haihusiki" (N/A). [signed_releases]
    Matokeo ya mradi ni pamoja na msimbo wa chanzo na matokeo yoyote yaliyozalishwa pale inapohusika (k.m., mifumo inayotekelezeka, vifurushi, na vyombo). Matokeo yaliyozalishwa YANAWEZA kuwekwa saini tofauti na msimbo wa chanzo. Hizi ZINAWEZA kutekelezwa kama lebo za git zilizowekwa saini (kwa kutumia saini za kidijitali za kriptologia). Miradi YAWEZA kutoa matokeo yaliyozalishwa tofauti na zana kama vile git, lakini katika hali hizo, matokeo tofauti LAZIMA yawekwe saini tofauti.

    Every release is cryptographically signed and independently verifiable. Each artifact carries a Sigstore bundle and a provenance attestation on its digest, built inside reusable workflows per GitHub's documented SLSA Build L3 construction, alongside sha256 sums, a per-artifact CycloneDX SBOM and a generated SPDX repository SBOM that is itself attested; a release step refuses to publish unless every expected asset is attached, and immutable releases are enabled so the assets and tag freeze at publish. Verification is a documented one-liner — gh attestation verify <artifact> -R rubentalstra/Veredictum --signer-workflow rubentalstra/Veredictum/.github/workflows/release-build.yml : https://veredictum.eu/docs/installation.html


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kuwa katika mfumo wa udhibiti wa toleo, kila lebo muhimu ya toleo (lebo ambayo ni sehemu ya toleo kuu, toleo dogo, au kurekebishwa udhaifu uliotangazwa hadharani) iwekwe saini kwa kriptologia na iweze kuthibitishwa kama ilivyoelezwa katika signed_releases. [version_tags_signed]

    Release tags are OpenPGP-signed by the maintainer key documented in MAINTAINERS.md, and this is enforced rather than customary: the refs/tags/v* ruleset (no bypass) requires a signature and forbids deleting or non-fast-forward-updating a tag, which protects the exact window in which a tag drives the release build. Every commit in the history is signature-verified under the main ruleset as well: https://github.com/rubentalstra/Veredictum/tags


  • Masuala mengine ya usalama


    Ya kutosha kwa nishani!

    Matokeo ya mradi LAZIMA yafanye ukaguzi wa pembejeo zote kutoka vyanzo visivyoaminika ili kuhakikisha ni halali (*orodha zinazokubalika*), na kukataa pembejeo zisizo halali, ikiwa kuna vizuizi vyovyote kwenye data kabisa. [input_validation]
    Kumbuka kuwa kulinganisha ingizo dhidi ya orodha ya "miundo mibaya" (aka *orodha za kukataza*) kwa kawaida haitoshi, kwa sababu washambuliaji mara nyingi wanaweza kuepuka orodha ya kukataza. Hasa, nambari zinabadilishwa kuwa miundo ya ndani na kisha kuangaliwa ikiwa ziko kati ya chini na juu zao (ikiwa ni pamoja), na vifungu vya maandishi vinaangaliwa ili kuhakikisha kuwa ni ruwaza halali za maandishi (k.m., UTF-8 halali, urefu, sintaksia, n.k.). Baadhi ya data inaweza kuhitaji kuwa "chochote kabisa" (k.m., kipakia faili), lakini hizi kwa kawaida zingekuwa nadra.

    Input is validated against a whitelist by construction, not sanitized after the fact. Artifact and party documents are read through strict typed constructors and refused on undeclared or duplicate keys; the catalogue itself is gated by veredictum validate, where zero findings is the only passing result (id uniqueness, citation resolution against the vendored specification text, binding completeness, and coverage of the enumerated wire surface); AQL and citation input is parsed by grammar-exact parsers that reject rather than guess; and every refusal is kept as its own pinned negative test, so a lenient acceptance is a failing test. The lint set removes the classic silent-acceptance paths (indexing_slicing, string_slice, as_conversions all denied). Every reader that parses outside input has a fuzz harness: https://github.com/rubentalstra/Veredictum/blob/main/fuzz/README.md


    Ya kutosha kwa nishani!

    Taratibu za kuimarisha ZINAPASWA kutumiwa katika programu iliyozalishwa na mradi ili kasoro za programu ziwe na uwezekano mdogo wa kusababisha udhaifu wa usalama. [hardening]
    Taratibu za kuimarisha zinaweza kujumuisha vichwa vya HTTP kama Sera ya Usalama wa Maudhui (CSP), bendera za mkusanyaji ili kupunguza mashambulizi (kama vile -fstack-protector), au bendera za mkusanyaji ili kuondoa tabia isiyofafanuliwa. Kwa madhumuni yetu upendeleo mdogo hauhesabiwi kuwa utaratibu wa kuimarisha (upendeleo mdogo ni muhimu, lakini tofauti).

    The container image is hardened and the hardening is machine-checked: a digest-pinned distroless base (gcr.io/distroless/cc-debian13:nonroot) with an explicit numeric USER 65532:65532 so an orchestrator does not have to resolve a name, no shell and no package manager in the runtime layer, a HEALTHCHECK, OCI metadata that a CI guard (scripts/checks/image-labels.sh) checks agrees with itself, hadolint over the Dockerfile on every pull request and Trivy over the published image weekly. The console binds to loopback unless the operator explicitly publishes it. On the process side the release profile keeps overflow-checks = true, and unsafe_code = forbid removes the memory-unsafety class outright: https://github.com/rubentalstra/Veredictum/blob/main/docker/Dockerfile


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe kesi ya uhakika inayosababisha kwa nini mahitaji yake ya usalama yanakidhi. Kesi ya uhakika LAZIMA ijumuishe: maelezo ya muundo wa tishio, utambulisho wazi wa mipaka ya kuaminiwa, hoja kwamba kanuni za muundo salama zimetumika, na hoja kwamba udhaifu wa kawaida wa utekelezaji wa usalama umekabiliana nao. (URL inahitajika) [assurance_case]
    Kesi ya uhakika ni "mwili wa ushahidi ulioandikwa unaotoa hoja inayoshawishi na halali kwamba seti maalum ya madai muhimu kuhusu mali za mfumo ziko na sababu za kutosha kwa programu maalum katika mazingira maalum" ("Uhakika wa Programu Kwa kutumia Miundo ya Kesi ya Uhakika Iliyopangwa", Thomas Rhodes et al, NIST Interagency Report 7608). Mipaka ya kuaminiwa ni mipaka ambapo data au utekelezaji hubadilisha kiwango chake cha kuaminiwa, k.m., mipaka ya seva katika programu ya kawaida ya wavuti. Ni ya kawaida kuorodhesha kanuni za muundo salama (kama vile Saltzer na Schroeer) na udhaifu wa kawaida wa utekelezaji wa usalama (kama vile OWASP top 10 au CWE/SANS top 25), na kuonyesha jinsi kila moja unavyokabiliana. Kesi ya uhakika ya BadgeApp inaweza kuwa mfano wenye manufaa. Hii inahusiana na documentation_security, documentation_architecture, na implement_secure_design.

    ASSURANCE_CASE.md is the assurance argument, and every row names a file in this repository so each claim can be opened and checked: https://github.com/rubentalstra/Veredictum/blob/main/ASSURANCE_CASE.md . § 1 states the assets an attacker would want (verdict integrity — a wrong green is the worst outcome the product has; record integrity across the bundle, the release tarball and the image; confidentiality of the operator's inputs). § 2 is the trust-boundary table: the catalogue and vendored specifications as trusted-and-gated (validate at zero findings, entry point named), the system under test as untrusted by definition (its responses are evidence in a comparison, never instructions, and it cannot move the reference it is measured against), the operator's IXIT holding credential references only so an inline secret is unrepresentable, every console #[server] fn as a public endpoint bound to loopback by default, and the published record as tamper-evident without this tool (byte-deterministic SHA-256 manifest plus an RFC 9580 detached signature that plain gpg --verify checks). § 3 pairs each security-relevant requirement with the check that fails on violation (unsafe_code = forbid, the denied panic and indexing families, overflow-checks, typed errors at every branching boundary). § 4 names the three rules enforced by review alone rather than hiding them — on the project's own principle that a rule with no failing check is a wish. § 5 states what the case does not claim: no formal verification, no console authentication by design, no sanitizing of what is recorded, and that a verified signature says nothing about the conditions the run executed under. The reporting route stays in SECURITY.md, and a stale claim on that page is handled as a defect in the assurance case.


 Uchanganuzi 2/2 ●

  • Uchambuzi tuli wa msimbo


    Ya kutosha kwa nishani!

    Mradi LAZIMA utumie angalau zana moja ya uchanganuzi tuli yenye sheria au mbinu za kutafuta udhaifu wa kawaida katika lugha au mazingira yaliyochanganuliwa, ikiwa kuna angalau zana moja ya FLOSS inayoweza kutekeleza kigezo hiki katika lugha iliyochaguliwa. [static_analysis_common_vulnerabilities]
    Zana za uchambuzi tuli ambazo zimeundwa hasa kutafuta udhaifu wa kawaida zina uwezekano mkubwa wa kuzipata. Hata hivyo, kutumia zana zozote za tuli kwa kawaida itasaidia kupata baadhi ya matatizo, kwa hivyo tunashauri lakini hatunahitaji hii kwa kiwango cha nishani ya 'kupita'.

    At least one analyser looks specifically for common vulnerability classes on every pull request: CodeQL runs its security query suites over the Rust and GitHub Actions sources on every push and pull request and again weekly, SonarQube Cloud publishes a security rating on the same events, zizmor audits the workflows for the Actions-specific classes (unpinned uses, credential-persisting checkouts, injectable contexts) at --min-severity=low, Trivy scans the published image, and cargo-deny checks the graph against the RustSec advisory database: https://github.com/rubentalstra/Veredictum/actions/workflows/codeql.yml


  • Uchambuzi wa msimbo wa nguvu za ziada


    Ya kutosha kwa nishani!

    Ikiwa programu iliyozalishwa na mradi inajumuisha programu iliyoandikwa kwa kutumia lugha isiyosalama ya kumbukumbu (k.m., C au C++), basi angalau zana moja ya nguvu (k.m., fuzzer au kitafutaji cha programu ya wavuti) LAZIMA itumike kwa kawaida kwa pamoja na utaratibu wa kugundua matatizo ya usalama wa kumbukumbu kama vile uandikaji zaidi wa kipengele. Ikiwa mradi hauzalishi programu iliyoandikwa katika lugha isiyosalama ya kumbukumbu, chagua "haihusiki" (N/A). [dynamic_analysis_unsafe]
    Mifano ya taratibu za kugundua matatizo ya usalama wa kumbukumbu ni pamoja na Address Sanitizer (ASAN) (inapatikana katika GCC na LLVM), Memory Sanitizer, na valgrind. Zana nyingine zinazoweza kutumika ni pamoja na thread sanitizer na undefined behavior sanitizer. Madai ya kila mahali pia yaweza kufanya kazi.

    There is no memory-unsafe code to analyse. unsafe_code = "forbid" applies to the whole workspace, and forbid cannot be relaxed by an attribute — not even #[allow] compiles under it — so introducing unsafe would require a deliberate change to stop inheriting the lint table rather than a local suppression. The libFuzzer harnesses still run over every outside-input reader with sanitizer instrumentation regardless: https://github.com/rubentalstra/Veredictum/blob/main/Cargo.toml



Unaweza kutumia zana na mifumo ya AI kupendekeza mabadiliko kupitia URL rahisi, kama vile https://www.bestpractices.dev/sw/projects/14252/choose/edit?osps_ac_01_01_status=Met&osps_ac_01_01_justification=GitHub+enforced. Angalia mfumo wetu wa mapendekezo ya otomatiki kwa jinsi ya kufanya hivyo. Data hii inapatikana chini ya Community Data License Agreement – Permissive, Version 2.0 (CDLA-Permissive-2.0). Hii inamaanisha kuwa Mpokeaji wa Data anaweza kushiriki Data, na au bila marekebisho, mradi Mpokeaji wa Data anapatanisha maandishi ya mkataba huu na Data iliyoshirikiwa. Tafadhali tambua Ruben Talstra na wachangiaji wa nishani ya Mazoea Bora ya OpenSSF.

Ingizo la nishani ya mradi linamilikiwa na: Ruben Talstra.
Ingizo liliundwa siku 2026-08-26 14:17:43 UTC, iliyosasishwa mara ya mwisho siku 2026-08-27 17:48:50 UTC. Ilipata mara ya mwisho nishani ya kupita siku 2026-08-27 15:20:01 UTC.