ClipSync

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

    End-to-end encrypted clipboard synchronization for macOS, Linux, and Windows, with a CLI, native desktop app, WebSocket relay, and shared mobile bindings. Paired devices can share text, images, and files.

    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.

    Assessment for the Rust workspace and support/packaging scripts in Jeon1691/clipsync. Separate native mobile-app repositories are outside this entry. Assessed security release: v0.1.16, commit 639000d60f1af1cc856fe20c61b60c84f9b2ab7b. Published artifacts and signatures were independently downloaded and verified for all five platforms; a one-byte tampered copy was rejected. https://github.com/Jeon1691/clipsync/releases/tag/v0.1.16 ; https://github.com/Jeon1691/clipsync/actions/runs/43676432941 . Maintainer knowledge and prior reporting history were personally confirmed on 2026-11-15. Evidence and warning dispositions: https://github.com/Jeon1691/clipsync/blob/v0.1.16/docs/best-practices-assessment.md ; https://github.com/Jeon1691/clipsync/blob/v0.1.16/docs/compiler-warnings.md . Full payload forward secrecy, measured broad coverage, blanket strict warnings, and native sanitizer coverage retain their stated limitations. No independent audit of the full protocol is claimed.

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

    The project is operated by one human maintainer. There is no second capable maintainer, unrelated substantial contributor or qualifying second-human review history. Bots and AI agents do not count. No unavailable reviewer approval is required in a way that would lock the owner out. https://github.com/Jeon1691/clipsync/blob/master/GOVERNANCE.md



    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.

    The project is operated by one human maintainer. There is no second capable maintainer, unrelated substantial contributor or qualifying second-human review history. Bots and AI agents do not count. No unavailable reviewer approval is required in a way that would lock the owner out. https://github.com/Jeon1691/clipsync/blob/master/GOVERNANCE.md


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

    Every inventoried first-party source/build file includes a project copyright statement and SPDX-License-Identifier:MIT, preserving shebangs and existing ownership. The source-header checker is run in CI. Generated locks and data fixtures are outside source-header insertion. https://github.com/Jeon1691/clipsync/blob/master/scripts/check-source-headers.py


 Udhibiti wa Mabadiliko 4/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 Git repository uses a common distributed version-control system. https://github.com/Jeon1691/clipsync/blob/master/CONTRIBUTING.md



    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 dated roadmap covers November2026 through November2027, intended work and non-goals, plus concrete small contributor tasks with verification expectations. https://github.com/Jeon1691/clipsync/blob/master/ROADMAP.md



    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 sole maintainer confirmed on2026-11-15 that the GitHub account uses a passkey/security key or TOTP. Governance requires2FA for all repository-write/private-security access and recommends cryptographic methods; no authentication secrets are published. https://github.com/Jeon1691/clipsync/blob/master/GOVERNANCE.md



    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.

    The sole maintainer confirmed on2026-11-15 that the GitHub account uses a passkey/security key or TOTP. Governance requires2FA for all repository-write/private-security access and recommends cryptographic methods; no authentication secrets are published. https://github.com/Jeon1691/clipsync/blob/master/GOVERNANCE.md


 Ubora 6/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.

    The contribution guide specifies style guides, enforced Rust formatting/lints, mandatory automated tests for major functionality, review checks and acceptance. https://github.com/Jeon1691/clipsync/blob/master/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 project is operated by one human maintainer. There is no second capable maintainer, unrelated substantial contributor or qualifying second-human review history. Bots and AI agents do not count. No unavailable reviewer approval is required in a way that would lock the owner out. https://github.com/Jeon1691/clipsync/blob/master/GOVERNANCE.md


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

    Verified native Linux amd64 reconstruction passed in https://github.com/Jeon1691/clipsync/actions/runs/43721162782 . Two environments independently reinstall the digest-pinned base, dated signed Debian packages and Rust 1.100, without shared application objects. All six outputs, native-package manifests and source archives match. Downloaded evidence independently reconciles source 38cdb4821c0e005c646ea0cdf26c4a246cef2b9e, tree dfa7f4a4b4a32ab20a90f6b7d3a4bc8bc41c68e5, identical to reviewed head 78396ea and merged master 756fa03. Report cleanup and upload passed. The exact upstream UniFFI deterministic-macro fix is backported with archive/license/full-patch evidence. Recipe and reproduction commands: https://github.com/Jeon1691/clipsync/blob/master/docs/builds.md . Scope is the six Linux products, not other platforms or archive packaging.


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

    Cargo test is the standard invocation. Push/default-branch and PR CI reports workspace, integration and platform tests on Linux/macOS/Windows, with minimum Rust checked separately. https://github.com/Jeon1691/clipsync/blob/master/.github/workflows/ci.yml



    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.

    Cargo test is the standard invocation. Push/default-branch and PR CI reports workspace, integration and platform tests on Linux/macOS/Windows, with minimum Rust checked separately. https://github.com/Jeon1691/clipsync/blob/master/.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]

    Final reviewed source 78396ea passed both complete hosted product suites with all twelve crates retained: Linux 5392/5665 lines (95.18%), 5785/6360 executable regions (90.96%); macOS 5823/6194 lines (94.01%), 6225/6892 regions (90.32%). LLVM executable regions plus an additional line threshold provide this project's Rust statement-coverage evidence. Only test code is excluded; unexecuted product paths, desktop and mobile stay in scope. Each host independently requires >=90% lines/regions and >=80% branches. Actual reports were downloaded and counters validated; platform denominators are not combined. https://github.com/Jeon1691/clipsync/actions/runs/43721162645 and https://github.com/Jeon1691/clipsync/blob/master/docs/testing.md .



    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]

    Final reviewed source 78396ea has actual LLVM branch instrumentation across all twelve product crates: Linux 856/1000 branches (85.60%) and macOS 943/1118 (84.35%). Both full hosted suites and the mandatory >=80% branch gate passed. Production paths are retained, test-only code is excluded, and source/per-file totals were independently validated. Each platform is reported separately; this does not claim Windows, device-app or external-native-library coverage. https://github.com/Jeon1691/clipsync/actions/runs/43721162645 and https://github.com/Jeon1691/clipsync/blob/master/docs/testing.md .


 Usalama 5/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]

    Merged v0.2.0 source defaults clients to verified HTTPS/WSS and the relay refuses to listen without a matching TLS certificate/private key and HTTPS public URL. Plain HTTP requires explicit CLIPSYNC_RELAY_ALLOW_HTTP=true for private TLS-proxy/local use; there is no automatic plaintext fallback. rustls supports TLS 1.2/1.3 with normal issuer/hostname verification; every configured extra root is parsed before constructing the platform verifier. Real binary/HTTP/WSS tests cover valid private roots, wrong issuer/hostname, plaintext rejection, configuration failures and bounded TLS handshakes. https://github.com/Jeon1691/clipsync/blob/master/docs/self-hosting.md and https://github.com/Jeon1691/clipsync/actions/runs/43721162620 .



    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]

    rustls supports TLS1.2/1.3 with normal certificate/hostname verification; reqwest and WebSocket handshakes verify before sending private headers. Configured extra roots extend trust rather than disabling verification. No accept-invalid path is used. https://github.com/Jeon1691/clipsync/blob/master/crates/clipsync-transport/src/tls.rs


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

    Website/repository/downloads are hosted on GitHub, explicitly accepted by the criterion. Actual response headers were checked:nonpermissiveCSP,HSTS,nosniff,X-Frame-Optionsdeny. https://github.com/Jeon1691/clipsync/blob/master/docs/best-practices-levels.md


  • 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-11-15 maintainer Jeon1691 personally confirmed reviewing PR16 source d0501a74e4d1d02160ac113bf1f542731163221a and its assurance case, including security requirements, authentication/key management, file, webhook and release trust boundaries and residual risks. This internal human design/security review is recorded separately from AI/tool analysis; no independent audit or two-person history is claimed. https://github.com/Jeon1691/clipsync/blob/master/docs/assurance-case.md



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

    Actual attestation-verified v0.1.16 CLI binaries were inspected:Linux PIE/NX/fullRELRO;macOS PIE without executable-stack opt-in;Windows ASLR/high-entropyVA/DEP. Mechanisms, reproduction and limits are documented. Non-root execution alone is not used as hardening evidence. https://github.com/Jeon1691/clipsync/blob/master/docs/hardening.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.

    Routine protocol and AEAD libFuzzer campaigns run with ASan and assertions; native macOS clipboard, daemon and mobile tests also run under ASan. The expanded native campaign passed 62 tests. Earlier 601-second pre-release protocol/AEAD campaigns had no findings. OS libraries and every FFI path are not claimed fully instrumented. https://github.com/Jeon1691/clipsync/blob/master/docs/testing.md



    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.

    Routine protocol and AEAD libFuzzer campaigns run with ASan and assertions; native macOS clipboard, daemon and mobile tests also run under ASan. The expanded native campaign passed 62 tests. Earlier 601-second pre-release protocol/AEAD campaigns had no findings. OS libraries and every FFI path are not claimed fully instrumented. https://github.com/Jeon1691/clipsync/blob/master/docs/testing.md



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

Ingizo la nishani ya mradi linamilikiwa na: develicit.
Ingizo liliundwa siku 2026-11-15 03:17:45 UTC, iliyosasishwa mara ya mwisho siku 2026-11-15 14:14:47 UTC. Ilipata mara ya mwisho nishani ya kupita siku 2026-11-15 04:37:02 UTC.