Artemis

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 14163 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/14163/badge)](https://www.bestpractices.dev/projects/14163)
au kwa kuweka hii katika HTML yako:
<a href="https://www.bestpractices.dev/projects/14163"><img src="https://www.bestpractices.dev/projects/14163/badge"></a>


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

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

        

 Misingi 3/5 ●

  • Jumla

    Kumbuka kwamba miradi mingine inaweza kutumia jina sawa.

    Artemis - Interactive Learning with Automated Feedback

    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


    Mradi LAZIMA ufikie kiwango cha nishani ya fedha. [achieve_silver]

  • Usimamizi wa mradi


    Mradi LAZIMA uwe 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.

    Multiple active maintainers share development, review, merge, and release responsibilities. The maintainer confirmed independent continuity access for at least two people. https://docs.artemis.tum.de/about/governance



    Mradi LAZIMA uwe na angalau wachangiaji wawili wasiohusika. (URL inahitajika) [contributors_unassociated]
    Wachangiaji wanahusianishwa ikiwa wanalipwa kufanya kazi na shirika moja (kama mwajiriwa au mkandarasi) na shirika lile linapata faida kutokana na matokeo ya mradi. Misaada ya kifedha haihesabiwi kuwa kutoka shirika sawa ikiwa inapitia mashirika mengine (k.m., misaada ya sayansi inayolipwa kwa mashirika tofauti kutoka serikali ya kawaida au chanzo cha NGO haifanyi wachangiaji kuhusianishwa). Mtu ni mchangiaji muhimu ikiwa amefanya michango isiyojulikana kwa mradi katika mwaka uliopita. Mifano ya viashiria vizuri vya mchangiaji muhimu ni: ameandika angalau mistari 1,000 ya msimbo, amechangia commits 50, au amechangia angalau kurasa 20 za nyaraka.

    Reviewed 2025-10-19 through 2026-10-19. Benedikt Fein (University of Passau, b-fein) made substantive merged documentation and programming-exercise changes: https://github.com/ls1intum/Artemis/pull/11583 and https://github.com/ls1intum/Artemis/pull/12661 . Eduard Frankford (University of Innsbruck, eduardfrankford) contributed a websocket deadlock fix and regression tests, lecture form improvements and a coverage-tooling correction: https://github.com/ls1intum/Artemis/pull/13834 , https://github.com/ls1intum/Artemis/pull/13965 and https://github.com/ls1intum/Artemis/pull/14243 . The maintainer confirmed the distinct university affiliations on 2026-10-19; staff listings corroborate them: https://www.fim.uni-passau.de/en/chair-for-software-engineering-ii/team and https://www.uibk.ac.at/de/informatik/team/ . These are non-trivial contributions; the numerical examples are not mandatory minimums.


  • Mengine


    Mradi LAZIMA ujumuishe tamko la leseni katika kila faili ya chanzo. Hii YAWEZA kufanyika kwa kujumuisha yafuatayo ndani ya maoni karibu na mwanzo wa kila faili: SPDX-License-Identifier: [maneno ya leseni ya SPDX kwa mradi]. [license_per_file]
    Hii pia YAWEZA kufanyika kwa kujumuisha tamko katika lugha asilia ikitambulisha leseni. Mradi pia YAWEZA kujumuisha URL thabiti inayoelekeza kwenye maandishi ya leseni, au maandishi kamili ya leseni. Kumbuka kwamba kigezo cha license_location kinahitaji leseni ya mradi iwe mahali pa kawaida. Angalia mafunzo haya ya SPDX kwa maelezo zaidi kuhusu maneno ya leseni ya SPDX. Kumbuka uhusiano na copyright_per_file, ambayo yaliyomo yake kwa kawaida yangetangulia maelezo ya leseni.

    The repository has an MIT LICENSE, but source files do not uniformly carry a license statement or SPDX identifier. Generated source needs a generator-level solution. https://github.com/ls1intum/Artemis/blob/develop/LICENSE


 Udhibiti wa Mabadiliko 2/4 ●

  • Hifadhi ya chanzo ya kudhibiti toleo ya hadharani


    Hifadhi ya chanzo ya mradi LAZIMA itumie programu ya kawaida ya kudhibiti toleo linalosambazwa (k.m., git au mercurial). [repo_distributed]
    Git haihitajiki kihususa na miradi inaweza kutumia programu ya udhibiti wa toleo iliyokusanyika (kama subversion) na sababu.

    The public repository uses Git with complete clone/fork support. https://github.com/ls1intum/Artemis



    Mradi LAZIMA utambulishe kazi ndogo ambazo zinaweza kufanywa na wachangiaji wapya au wa mara kwa mara. (URL inahitajika) [small_tasks]
    Utambulisho huu kwa kawaida unafanyika kwa kuweka alama masuala yaliyochaguliwa katika kifuatiliaji cha masuala kwa lebo moja au zaidi ambazo mradi unatumia kwa madhumuni hayo, k.m., up-for-grabs, first-timers-only, "Marekebisho madogo", microtask, au IdealFirstBug. Kazi hizi mpya hazihitaji kujumuisha kuongeza utendaji; zinaweza kuwa kuboresha nyaraka, kuongeza hali za majaribio, au chochote kingine kinachosaidia mradi na kusaidia mchangiaji kuelewa zaidi kuhusu mradi.

    The good first issue label identifies tasks for new contributors, and CONTRIBUTING links it. https://github.com/ls1intum/Artemis/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22



    Mradi LAZIMA uhitaji uthibitishaji wa mambo mawili (2FA) kwa wasanidi programu ili kubadilisha hifadhi ya kati au kupata data nyeti (kama ripoti za faragha za udhaifu). Utaratibu huu wa 2FA YAWEZA kutumia taratibu bila taratibu za usimbuaji kama SMS, ingawa hii hairuhusiwi. [require_2FA]

    The authenticated GitHub organization API still reported two_factor_requirement_enabled=false for ls1intum on 2026-10-19. No alternative requirement covering all central-repository changes and private-vulnerability-report access has been verified. Individual accounts using 2FA do not establish mandatory enforcement. Coordinate any account-access changes with authorized organization administrators. https://github.com/ls1intum



    Uthibitishaji wa mambo mawili (2FA) ya mradi INAPASWA kutumia taratibu za usimbuaji ili kuzuia ujigeuzi. Uthibitishaji wa 2FA unaotegemea Huduma ya Ujumbe Mfupi (SMS), peke yake, HAUKIDHI kigezo hiki, kwa kuwa haufichui. [secure_2FA]
    Utaratibu wa 2FA unaokidhi kigezo hiki unaweza kuwa programu ya Nywila ya Mara Moja Inayotegemea Muda (TOTP) ambayo inazalisha kiotomatiki msimbo wa uthibitishaji unaobadilika baada ya muda fulani. Kumbuka kwamba GitHub inasaidia TOTP.

 Ubora 7/7 ●

  • Viwango vya msimbo


    Mradi LAZIMA uandike mahitaji yake ya kukagua msimbo, pamoja na jinsi ukaguzi wa nambari unafanywa, nini lazima ichunguzwe, na nini kinachohitajika ili ikubalike. (URL inahitajika) [code_review_standards]
    Angalia pia two_person_review na contribution_requirements.

    Contribution and reviewer guidelines document author tasks, four-reviewer expectations, feature-maintainer approval, final review, and CI readiness. https://docs.artemis.tum.de/developer/reviewer-guidelines and https://github.com/ls1intum/Artemis/blob/develop/.github/CONTRIBUTING.md



    Mradi LAZIMA uwe na angalau 50% ya marekebisho yote yaliyopendekezwa kupitishwa kabla ya kutolewa na mtu mwingine isipokuwa mwandishi, ili kuamua ikiwa ni marekebisho ya manufaa na huru ya masuala yaliyojulikana ambayo yangepingana na ujumuishaji wake [two_person_review]

    The 2026-10-19 OpenSSF Scorecard scan at merged revision 3d0bd7dfb4cd077394cc7cc22293855ed0dad9d5 found 27 of 30 changesets approved by reviewers, above the 50% threshold (Code-Review 9/10; overall Scorecard 9.0). An independent check of the 28 PR merges among the latest 30 first-parent commits found 27 had a non-author human approval before merge, including all three coverage PRs. This records recent practice; reassess the preceding release interval when updating the criterion. https://api.securityscorecards.dev/projects/github.com/ls1intum/Artemis ; https://github.com/ls1intum/Artemis/pull/14286 ; https://github.com/ls1intum/Artemis/pull/14280 ; https://github.com/ls1intum/Artemis/pull/14279


  • Mfumo wa ujenzi unaofanya kazi


    Mradi LAZIMA uwe na ujenzi unaorudiwa. Ikiwa hakuna ujenzi unaofanyika (k.m., lugha za uandishi ambapo msimbo wa chanzo unatumika moja kwa moja badala ya kukusanywa), chagua "haihusiki" (N/A). (URL inahitajika) [build_reproducible]
    Ujenzi unaorudiwa unamaanisha kwamba pande nyingi zinaweza kwa uhuru kurudia mchakato wa kuzalisha taarifa kutoka faili za chanzo na kupata matokeo sawa ya biti-kwa-biti. Katika hali fulani, hii inaweza kutatuliwa kwa kulazimisha mpangilio fulani wa aina. Wasanidi wa JavaScript wanaweza kuzingatia kutumia npm shrinkwrap na webpack OccurrenceOrderPlugin. Watumiaji wa GCC na clang wanaweza kupata chaguo la -frandom-seed kuwa na manufaa. Mazingira ya ujenzi (ikijumuisha zana) kwa kawaida yanaweza kufafanuliwa kwa pande za nje kwa kubainisha hash ya usimbuaji ya chombo maalum au mashine ya kawaida ambayo wanaweza kutumia kwa kujenga upya. Mradi wa majengo yanayorudiwa una nyaraka za jinsi ya kufanya hivi.

    On 2026-10-19 the project maintainer confirmed that another maintainer independently built the same source revision in a separate build and obtained the identical complete WAR SHA-256. This records the maintainer attestation of independent bit-for-bit reproduction. The documented release-build procedure regenerates the production client, compiled server and bundled SBOMs using -Preproducible, frozen dependencies, controlled toolchain inputs and no reused build output: https://docs.artemis.tum.de/developer/best-practices#repeatable-builds . Implementation and the earlier controlled-environment build pair are documented in https://github.com/ls1intum/Artemis/pull/14258 . The earlier same-checkout pair establishes repeatability; the separately confirmed independent rebuild supplies the Gold evidence. A container image is one possible way to describe a build environment, not a mandatory form of this criterion.


  • Seti ya majaribio otomatiki


    Seti ya majaribio LAZIMA iweze kuitwa kwa njia ya kawaida kwa lugha hiyo. (URL inahitajika) [test_invocation]
    Kwa mfano, "make check", "mvn test", au "rake test" (Ruby).

    The standard Gradle wrapper test and pnpm Vitest commands are documented. https://docs.artemis.tum.de/developer/setup



    Mradi LAZIMA utekeleze ujumuishaji wa kuendelea, ambapo msimbo mpya au uliobadilishwa unajumuishwa mara kwa mara katika hifadhi ya msimbo ya kati na majaribio ya kiotomatiki yanafanywa kwenye matokeo. (URL inahitajika) [test_continuous_integration]
    Katika hali nyingi hii inamaanisha kwamba kila msanidi programu anayefanya kazi kikamilifu kwenye mradi anajumuisha angalau kila siku.

    The CI workflow tests pull requests and protected-branch pushes and publishes test reports. https://github.com/ls1intum/Artemis/blob/develop/.github/workflows/ci.yml



    Mradi LAZIMA uwe na seti ya majaribio ya kiotomatiki ya FLOSS ambayo inatoa angalau 90% ya ufikio wa tamko ikiwa kuna angalau zana moja ya FLOSS ambayo inaweza kupima kigezo hiki katika lugha iliyochaguliwa. [test_statement_coverage90]

    Client Vitest statements: 82,875/90,018 (92.06%) in complete successful CI https://github.com/ls1intum/Artemis/actions/runs/39163316687 . Client production sources match merged develop 3d0bd7dfb4cd077394cc7cc22293855ed0dad9d5. Complete successful seven-shard server CI for merged PR #14286 reports 91.98% JaCoCo instructions, the Java statement proxy: https://github.com/ls1intum/Artemis/actions/runs/39164068412 . Recombining all seven passing execution artifacts from that run and https://github.com/ls1intum/Artemis/actions/runs/39163868255 plus https://github.com/ls1intum/Artemis/actions/runs/39160461237 against the merged production classes gives 534,108/577,958 instructions (92.41%) and 99,314/107,851 lines (92.08%), preserving existing exclusions. This is a recomputed union of complete successful CI runs, not a new standalone develop run. The README weighted line badge is not used as statement evidence.



    Mradi LAZIMA uwe na seti ya jaribio zilizofanywa kiotomatiki za FLOSS ambazo zinatoa angalau asilimia 80 ya uangaliaji wa tawi ikiwa kuna angalau zana moja ya FLOSS inayoweza kupima kigezo hiki katika lugha iliyochaguliwa. [test_branch_coverage80]

    Client Vitest branches: 33,791/42,138 (80.19%) in complete successful CI https://github.com/ls1intum/Artemis/actions/runs/39163316687 ; client production sources match merged develop 3d0bd7dfb4cd077394cc7cc22293855ed0dad9d5. Complete successful seven-shard server CI for merged PR #14286 reports 38,456/47,889 branches (80.30%): https://github.com/ls1intum/Artemis/actions/runs/39164068412 . Recombining passing execution data from all seven shards of that run plus https://github.com/ls1intum/Artemis/actions/runs/39163868255 and https://github.com/ls1intum/Artemis/actions/runs/39160461237 against merged production classes gives 38,842/47,897 branches (81.09%), with existing exclusions. The recomputation is not a new standalone CI run. Both application language suites exceed 80%.


 Usalama 3/5 ●

  • 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.

    Programu iliyozalishwa na mradi LAZIMA isaidie 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 LAZIMA zizimwe 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]

    HTTPS and SSH are supported, and operators must protect external traffic. Some distributed deployment links use plaintext protocols inside an operator-controlled private network; secure deployment requires isolation or additional TLS termination. This exception is documented rather than claiming universal TLS defaults. https://github.com/ls1intum/Artemis/blob/develop/.github/SECURITY.md#infrastructure-and-transport-security



    Programu iliyozalishwa na mradi LAZIMA, ikiwa inasaidia au inatumia TLS, isaidie angalau toleo la TLS 1.2. Kumbuka kwamba kabla ya TLS kuitwa SSL. Ikiwa programu haitumii TLS, chagua "haihusiki" (N/A). [crypto_tls12]

    Supported Java/Node runtimes and the documented production TLS configuration support TLS 1.2 and later; external reverse-proxy TLS configuration remains the operator responsibility. https://github.com/ls1intum/Artemis/blob/develop/src/main/resources/config/application-prod.yml


  • Utoaji salama dhidi ya mashambulizi ya mtu-katikati (MITM)


    Tovuti ya mradi, hifadhi (ikiwa inapatikana kupitia wavuti), na tovuti ya kupakua (ikiwa ni tofauti) LAZIMA ijumuishe vichwa muhimu vya kuimarisha na thamani zisizo na ruhusa. (URL inahitajika) [hardened_site]
    Kumbuka kwamba GitHub na GitLab zinajulikana kukidhi hii. Tovuti kama vile https://securityheaders.com/ zinaweza kuangalia hii haraka. Vichwa muhimu vya kuimarisha ni: Sera ya Usalama wa Maudhui (CSP), Usalama wa Usafiri wa HTTP Mkali (HSTS), X-Content-Type-Options (kama "nosniff"), na X-Frame-Options. Tovuti za wavuti zilizo za tuli kabisa bila uwezo wa kuingia kupitia kurasa za wavuti zinaweza kuacha baadhi ya vichwa vya kuimarisha na hatari ndogo, lakini hakuna njia ya kuaminika ya kugundua tovuti kama hizo, kwa hivyo tunahitaji vichwa hivi hata kama ni tovuti za tuli kabisa.

    Rechecked HTTPS GET responses on 2026-10-19. https://artemis.tum.de/ now returns HSTS, X-Content-Type-Options: nosniff, X-Frame-Options: DENY, and Content-Security-Policy. https://docs.artemis.tum.de/ returns none of those four headers. Gold explicitly requires them even for fully static sites. Configure the documentation hosting/proxy response headers and verify all project, repository and download endpoints before marking Met.


  • Masuala mengine ya usalama


    Mradi LAZIMA uwe umefanya ukaguzi wa usalama ndani ya miaka 5 iliyopita. Ukaguzi huu LAZIMA uzingatie mahitaji ya usalama na mpaka wa usalama. [security_review]
    Hii YAWEZA kufanywa na wanachama wa mradi na/au tathmini huru. Tathmini hii YAWEZA kusaidiwa na zana za uchambuzi za tuli na zenye nguvu, lakini lazima pia kuwe na ukaguzi wa binadamu ili kutambua matatizo (hasa katika muundo) ambayo zana haziwezi kugundua.

    On 2026-10-19 the project maintainer confirmed monthly internal human security reviews by the core maintainer team, including the documented security requirements and trust boundaries. This meets the five-year window. The reviewed requirements and boundaries are documented at https://docs.artemis.tum.de/developer/security-assurance and https://github.com/ls1intum/Artemis/blob/develop/.github/SECURITY.md#security-audits-and-open-source-transparency . The confirmation concerns actual human reviews; an assurance document or automated scans alone are not treated as substitutes. Confidential findings need not be published in this entry.



    Taratibu za kuimarisha LAZIMA zitumike katika programu iliyozalishwa na mradi ili kasoro za programu ziwe na uwezekano mdogo wa kusababisha udhaifu wa usalama. (URL inahitajika) [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).

    Production startup rejects published default credentials; documented headers, rendering restrictions, build isolation and security analysis provide defense in depth. https://github.com/ls1intum/Artemis/blob/develop/.github/SECURITY.md


 Uchanganuzi 2/2 ●

  • Uchambuzi wa msimbo wa nguvu za ziada


    Mradi LAZIMA utumie angalau zana moja ya uchambuzi wenye nguvu kwa toleo lolote lililopendekezwa kuu la uzalishaji wa programu iliyozalishwa na mradi kabla ya kutolewa kwake. [dynamic_analysis]
    Zana ya uchambuzi wa nguvu inachunguza programu kwa kuitekeleza na ingizo maalum. Kwa mfano, mradi YAWEZA kutumia zana ya fuzzing (k.m., American Fuzzy Lop) au kitafutaji cha programu ya wavuti (k.m., OWASP ZAP au w3af). Katika hali fulani mradi wa OSS-Fuzz unaweza kuwa tayari kutumia majaribio ya fuzz kwenye mradi wako. Kwa madhumuni ya kigezo hiki zana ya uchambuzi wa nguvu inahitaji kubadilisha ingizo kwa njia fulani kutafuta aina mbalimbali za matatizo au kuwa seti kiotomatiki ya majaribio yenye angalau asilimia 80 ya ukaguzi wa tawi. Ukurasa wa Wikipedia kuhusu uchambuzi wa nguvu na ukurasa wa OWASP kuhusu fuzzing hutambulisha baadhi ya zana za uchambuzi wa nguvu. Zana za uchambuzi ZINAWEZA kuzingatia kutafuta udhaifu wa usalama, lakini hii haihitajiki.

    On 2026-10-19 the project maintainer confirmed that, before every proposed major production release, maintainers require successful complete server and client test runs for the release candidate, review runtime failures and coverage, and resolve significant findings before release. Both automated suites exceed 80% branch coverage, qualifying as dynamic-analysis tools under this criterion. Server complete passing CI: https://github.com/ls1intum/Artemis/actions/runs/39164068412 ; client complete passing CI: https://github.com/ls1intum/Artemis/actions/runs/39163316687 . Coverage and runtime-assertion evidence: https://github.com/ls1intum/Artemis/pull/14289 . This records the human pre-release review practice; the release: published workflow is not used to prove analysis before publication. Fuzzing remains outside the current scope.



    Mradi INAPASWA kujumuisha madai mengi ya muda wa kutekeleza katika programu inayozalisha na kuangalia madai hayo wakati wa uchambuzi wenye nguvu. [dynamic_analysis_enable_assertions]
    Kigezo hiki hakipendekezi kuwezesha madai wakati wa uzalishaji; hilo ni kabisa kwa mradi na watumiaji wake kuamua. Lengo la kigezo hiki ni badala yake kuboresha ugunduzaji wa hitilafu wakati wa uchambuzi wa nguvu kabla ya kusambazwa. Kuwezesha madai katika matumizi ya uzalishaji ni tofauti kabisa na kuwezesha madai wakati wa uchambuzi wa nguvu (kama vile majaribio). Katika hali fulani kuwezesha madai katika matumizi ya uzalishaji ni busara sana (hasa katika vipengele vya uadilifu wa juu). Kuna hoja nyingi dhidi ya kuwezesha madai katika uzalishaji, k.m., maktaba hazipaswi kuvuruga waita, uwepo wao unaweza kusababisha kukataliwa na maduka ya programu, na/au kuamilisha madai katika uzalishaji kunaweza kufunua data za faragha kama vile funguo za faragha. Kumbuka kwamba katika usambazaji mwingi wa Linux NDEBUG haijafafanuliwa, hivyo C/C++ assert() kwa chaguo-msingi itawezeshwa kwa uzalishaji katika mazingira hayo. Inaweza kuwa muhimu kutumia utaratibu tofauti wa madai au kufafanua NDEBUG kwa uzalishaji katika mazingira hayo.

    Delivered server code has hundreds of Bean Validation runtime contracts, Spring Assert guards, and explicit constructor/invariant checks, including WorkerSettings. Tests exercise valid and invalid inputs against these production checks; these are not merely assertions inside test code. On 2026-10-19 the configured Gradle test task was inspected: enableAssertions=true and JVM arguments include -ea. https://github.com/ls1intum/Artemis/blob/develop/gradle/test.gradle ; https://docs.gradle.org/current/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:enableAssertions ; https://github.com/ls1intum/Artemis/blob/develop/src/main/java/de/tum/cit/aet/artemis/aiworker/config/WorkerSettings.java ; https://github.com/ls1intum/Artemis/blob/develop/src/test/java/de/tum/cit/aet/artemis/aiworker/api/WorkerBoundaryContractsTest.java . Full successful CI: https://github.com/ls1intum/Artemis/actions/runs/39164068412 . Production JVM assertion policy is a separate operator decision.



Unaweza kutumia zana na mifumo ya AI kupendekeza mabadiliko kupitia URL rahisi, kama vile https://www.bestpractices.dev/sw/projects/14163/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 Stephan Krusche na wachangiaji wa nishani ya Mazoea Bora ya OpenSSF.

Ingizo la nishani ya mradi linamilikiwa na: Stephan Krusche.
Ingizo liliundwa siku 2026-08-19 23:37:57 UTC, iliyosasishwa mara ya mwisho siku 2026-10-19 12:17:00 UTC. Ilipoteza mara ya mwisho nishani ya kupita siku 2026-10-17 11:01:01 UTC. Ilipata mara ya mwisho nishani ya kupita siku 2026-10-17 11:03:02 UTC.