maalik-e-makaan

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


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

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

        

 Misingi 13/13 ●

  • Jumla

    Kumbuka kwamba miradi mingine inaweza kutumia jina sawa.

    Tenant and property management for Pakistani landlords, in English and Urdu: rent, receipts, deposits, late fees and WhatsApp reminders. Flutter (Android, iOS, web) on Supabase, with an Astro website and TLA+, Lean and Z3 models of the money and concurrency code.

    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.

  • Maudhui ya kimsingi ya tovuti ya mradi


    Ya kutosha kwa nishani!

    Tovuti ya mradi LAZIMA ieleze kwa ufupi programu inafanya nini (inasuluhu tatizo gani?). [description_good]
    Hii LAZIMA iwe katika lugha ambayo watumiaji watarajiwa wanaweza kuelewa (k.m., inatumia lugha ya kiufundi kidogo).

    The README opens by saying in plain words what the software is for. It is tenant and property management for Pakistani landlords, in English and Urdu, that replaces registers, spreadsheets and WhatsApp threads with one ledger, and it lists the problems it handles: cash rent with numbered receipts, dues and late fees, caretakers who collect for overseas owners, police registration, tax-year statements and reminders. The website's home page says the same in English and Urdu ("Rent, receipts and records for Pakistani landlords").

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/README.md


    Ya kutosha kwa nishani!

    Tovuti ya mradi LAZIMA itoe habari juu ya jinsi ya: kupata, kutoa maoni (kama ripoti za hitilafu au maboresho), na kuchangia kwenye programu. [interact]

    The source is in the public GitHub repository, which every page of the website links to in its footer, and the README's Getting started section explains how to build and run it. From v1.0.0, release-please publishes GitHub Releases carrying the Android, web and unsigned iOS builds, SHA256SUMS and signed build-provenance attestations. Feedback goes through the bug-report and feature-request issue forms (blank issues are turned off, and security reports go to private advisories), and the README's Contributing section links to CONTRIBUTING.md.

    URL: https://github.com/ar27111994/maalik-e-makaan#readme


    Ya kutosha kwa nishani!

    Habari juu ya jinsi ya kuchangia LAZIMA ieleze mchakato wa uchangiaji (kwa mfano, je! Maombi ya kuvuta yanatumika?) (URL inahitajika) [contribution]
    Tunafikiria kuwa miradi kwenye GitHub hutumia maswala na kuvuta maombi isipokuwa palipoonyeshwa vingine. Habari hii inaweza kuwa fupi, kwa mfano, ikisema kuwa mradi hutumia maombi ya kuvuta, msako wa suala, au machapisho kwenye orodha ya barua (ipi?)

    CONTRIBUTING.md describes the process. Bugs and ideas go through the GitHub issue forms. Changes come as pull requests that must pass the same make targets CI runs. Pull requests are squash-merged, so the title must follow Conventional Commits with a scope from commitlint.config.mjs, and the pull-request template lists what each one must describe and check.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/CONTRIBUTING.md


    Ya kutosha kwa nishani!

    Habari juu ya jinsi ya kuchangia INAPASWA kujumuisha mahitaji ya michango inayokubalika (k.m., rejeleo la kiwango chochote kinachohitajika cha usimbaji). (URL inahitajika) [contribution_requirements]

    CONTRIBUTING.md sets the requirements. A change must pass make format-check analyze lint, and make test (very_good_analysis for Dart, deno lint for the Edge Functions); commits follow Conventional Commits; and database changes come as new migrations with pgTAP tests that keep the lock order. Money must be whole paisa, and user-facing text must exist in English and Urdu. Changes must meet WCAG 2.2 AA, contain no real personal data, and record dependency changes in THIRD_PARTY_NOTICES.md. The pull-request template repeats these as a checklist.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/CONTRIBUTING.md


  • Leseni ya FLOSS


    Ya kutosha kwa nishani!

    Programu iliyozalishwa na mradi LAZIMA itolewa kama FLOSS. [floss_license]
    FLOSS ni programu iliyotolewa kwa njia inayokidhi Ufafanuzi wa Chanzo Wazi au Ufafanuzi wa Programu Huria. Mifano ya leseni kama hizo ni pamoja na CC0, MIT, BSD 2-clause, BSD 3-clause revised, Apache 2.0, Lesser GNU General Public License (LGPL), na GNU General Public License (GPL). Kwa madhumuni yetu, hii inamaanisha kuwa leseni LAZIMA iwe: Programu YAWEZA pia kupatiwa leseni kwa njia nyingine (k.m., "GPLv2 au ya kibinafsi" inakubaliwa).

    Everything the project produces is released under the MIT licence, as LICENSE and the package LICENSE files state. That covers the app, the mm_core and mm_ui packages, the database migrations, the Edge Functions, the website and the tooling. Third-party packages and fonts keep their own licences, which THIRD_PARTY_NOTICES.md lists.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/LICENSE

    The MIT license is approved by the Open Source Initiative (OSI).


    Ya kutosha kwa nishani!

    INAPENDEKEZA kwamba leseni yoyote inayohitajika kwa programu iliyozalishwa na mradi iwe imeidhinishwa na Open Source Initiative (OSI). [floss_license_osi]
    OSI inatumia mchakato mgumu wa uidhinishaji kuamua ni leseni zipi ni OSS.

    The project uses the MIT licence, which the Open Source Initiative has approved.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/LICENSE


    Ya kutosha kwa nishani!

    Mradi LAZIMA uweke leseni za matokeo yake mahali pa kawaida katika hazina yake ya chanzo. (URL inahitajika) [license_location]
    Desturi moja ni kuweka leseni kama faili ya ngazi ya juu inayoitwa LICENSE au COPYING, ambayo YAWEZA kufuatiwa na kiendelezi kama ".txt" au ".md". Desturi mbadala ni kuwa na saraka inayoitwa LICENSES inayohifadhi faili za leseni; faili hizi kwa kawaida zinaitwa kama kitambulisho chao cha leseni ya SPDX kikifuatiwa na kiendelezi kinachofaa, kama ilivyoelezwa katika Maelezo ya REUSE. Kumbuka kwamba kigezo hiki ni mahitaji tu kwenye hazina ya chanzo. Huhitaji kuingiza faili ya leseni wakati wa kuzalisha kitu kutoka kwenye msimbo wa chanzo (kama programu inayotekelezeka, kifurushi, au chombo). Kwa mfano, wakati wa kuzalisha kifurushi cha R kwa Mtandao wa Kumbukumbu Kamili wa R (CRAN), fuata mazoea ya kawaida ya CRAN: ikiwa leseni ni leseni ya kawaida, tumia maelezo mafupi ya kawaida ya leseni (ili kuepuka kusakinisha nakala nyingine ya maandishi) na orodhesha faili ya LICENSE katika faili ya kutengwa kama .Rbuildignore. Vivyo hivyo, wakati wa kuunda kifurushi cha Debian, unaweza kuweka kiungo katika faili ya hakimiliki kwa maandishi ya leseni katika /usr/share/common-licenses, na utenge faili ya leseni kutoka kwenye kifurushi kilichoundwa (k.m., kwa kufuta faili baada ya kuita dh_auto_install). Tunashauri jumuisha maelezo ya leseni yanayoweza kusomwa na mashine katika miundo iliyozalishwa mahali inapofaa.

    The licence is in the standard place: a top-level LICENSE file (MIT, copyright 2026 Ahmed Rehan). The Dart packages carry their own copies in packages/mm_core/LICENSE and packages/mm_ui/LICENSE, and the README's Licence section links to it.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/LICENSE


  • Nyaraka


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe nyaraka za msingi za programu iliyozalishwa na mradi. [documentation_basics]
    Nyaraka hizi lazima ziwe katika vyombo fulani (kama maandishi au video) vinavyojumuisha: jinsi ya kuisakinisha, jinsi ya kuianzisha, jinsi ya kuitumia (huenda ikijumuisha mafunzo kwa kutumia mifano), na jinsi ya kuitumia kwa usalama (k.m., nini cha kufanya na nini cha kutofanya) ikiwa hiyo ni mada inayofaa kwa programu. Nyaraka za usalama lazima zisiwe ndefu. Mradi YAWEZA kutumia viungo vya hypertext kwa nyenzo zisizo za mradi kama nyaraka. Ikiwa mradi hauzalishi programu, chagua "haihusiki" (N/A).

    Installing and starting the software is covered in two places. The README's Getting started section lists the prerequisites, make bootstrap and how to run the app against a local Supabase stack, and docs/operations.md covers running it in production (secrets, health checks, hosting, deployment, backups). The website's How it works, Features and FAQ pages explain how to use it, and docs/uat.md walks through 14 landlord journeys with screenshots. Secure use is covered by the FAQ (roles, masked CNICs, private document storage), the README's Security section, SECURITY.md (the app refuses to start with a secret key) and docs/operations.md's Edge Function secrets and token handling.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/README.md#getting-started


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe nyaraka za marejeleo zinazofafanua kiolesura cha nje (ingizo na matokeo) cha programu iliyozalishwa na mradi. [documentation_interface]
    Nyaraka za kiolesura cha nje zinaeleza kwa mtumiaji wa mwisho au msanidi jinsi ya kuitumia. Hii itajumuisha kiolesura chake cha programu ya programu (API) ikiwa programu ina. Ikiwa ni maktaba, andika madarasa/aina kuu na mbinu/vitendakazi vinavyoweza kuitwa. Ikiwa ni programu ya wavuti, fafanua kiolesura chake cha URL (mara nyingi kiolesura chake cha REST). Ikiwa ni kiolesura cha mstari wa amri, andika vigezo na chaguo zinazosaidia. Katika hali nyingi ni bora ikiwa nyingi ya nyaraka hizi zinazalishwa kiotomatiki, ili nyaraka hizi zibaki zikisawazishwa na programu inavyobadilika, lakini hii haihitajiki. Mradi YAWEZA kutumia viungo vya hypertext kwa nyenzo zisizo za mradi kama nyaraka. Nyaraka ZIWEZA kuzalishwa kiotomatiki (ambapo ni vitendo hii mara nyingi ndiyo njia bora ya kufanya hivyo). Nyaraka za kiolesura cha REST zinaweza kuzalishwa kwa kutumia Swagger/OpenAPI. Nyaraka za kiolesura cha msimbo ZINAWEZA kuzalishwa kwa kutumia zana kama vile JSDoc (JavaScript), ESDoc (JavaScript), pydoc (Python), devtools (R), pkgdown (R), na Doxygen (nyingi). Kuwa na maoni tu katika msimbo wa utekelezaji haitoshi kutosheleza kigezo hiki; kunahitaji kuwa na njia rahisi ya kuona habari bila kusoma kupitia msimbo wote wa chanzo. Ikiwa mradi hauzalishi programu, chagua "haihusiki" (N/A).

    End users work through the app's screens, which the website's How it works and Features pages describe step by step. The backend API is documented in docs/architecture/permissions.md, which maps each action to the roles allowed to perform it and the RPC or row-level-security rule behind it (for example record_payment, void_payment). The generated supabase/functions/_shared/database.types.ts gives every RPC's arguments and return type. docs/operations.md documents the Edge Function endpoints, such as GET /functions/v1/health and its 200 and 503 responses, and packages/mm_core/README.md lists the domain library's modules.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/docs/architecture/permissions.md


  • Mengine


    Ya kutosha kwa nishani!

    Tovuti za mradi (tovuti, hifadhi, na URL za kupakua) LAZIMA zisaidie HTTPS kwa kutumia TLS. [sites_https]
    Hii inahitaji kwamba URL ya ukurasa wa nyumbani wa mradi na URL ya hifadhi ya udhibiti wa toleo vianze na "https:", si "http:". Unaweza kupata vyeti vya bure kutoka Let's Encrypt. Miradi YAWEZA kutekeleza kigezo hiki kwa kutumia (kwa mfano) GitHub pages, GitLab pages, au SourceForge project pages. Ikiwa unasaidia HTTP, tunakuhimiza uelekeze trafiki ya HTTP kwenda HTTPS.

    The repository, its issues and its release downloads are on GitHub, which serves only HTTPS. Vercel serves the website (maalik-e-makaan-site.vercel.app) and the web app (maalik-e-makaan.vercel.app) over HTTPS. website/vercel.json adds Strict-Transport-Security and a CSP with upgrade-insecure-requests, and the website build rejects any SITE_URL or PUBLIC_APP_URL that is not https (website/src/config/urls.ts).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/website/vercel.json


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na taratibu moja au zaidi za majadiliano (ikiwa ni pamoja na mabadiliko yaliyopendekezwa na masuala) yenye utafutaji, inaruhusu ujumbe na mada kuelekezwa kwa URL, inaruhusu watu wapya kushiriki katika baadhi ya majadiliano, na haihitaji usakinishaji wa upande wa mteja wa programu ya kibinafsi. [discussion]
    Mifano ya taratibu zinazokubalika ni pamoja na orodha za barua pepe zilizohifadhiwa, majadiliano ya suala la GitHub na ombi la kuvuta, Bugzilla, Mantis, na Trac. Taratibu za majadiliano yasiyo ya wakati mmoja (kama IRC) zinakubaliwa ikiwa zinakidhi vigezo hivi; hakikisha kuna utaratibu wa kuhifadhi unaoelekezwa kwa URL. JavaScript ya kibinafsi, ingawa haikubalika, inaruhusiwa.

    Discussion happens in GitHub issues (bug-report and feature-request forms) and pull requests. Both are public, searchable and addressable by URL, open to anyone with a free GitHub account, and usable in any browser with no proprietary client software. The website's FAQ, privacy and terms pages point readers to the issue tracker.

    URL: https://github.com/ar27111994/maalik-e-makaan/discussions


    Ya kutosha kwa nishani!

    Mradi UNAPASWA kutoa nyaraka kwa Kiingereza na uweze kukubali ripoti za hitilafu na maoni kuhusu msimbo kwa Kiingereza. [english]
    Kiingereza kwa sasa ni lingua franca ya teknolojia ya kompyuta; kusaidia Kiingereza huongeza idadi ya wasanidi na wakaguzi tofauti wa uwezekano duniani kote. Mradi unaweza kukidhi kigezo hiki hata ikiwa lugha ya msingi ya wasanidi wake wakuu si Kiingereza.

    All project and developer documentation is in English: the README, CONTRIBUTING.md, SECURITY.md, docs/, code comments and the issue and pull-request forms. Bug reports and comments about code are accepted in English. User-facing text is also provided in Urdu.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/README.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA utunzwe. [maintained]
    Kama kiwango cha chini, mradi unapaswa kujaribu kujibu ripoti za tatizo muhimu na udhaifu. Mradi unaofuata kwa bidii nishani pengine unatengenezwa. Miradi yote na watu wana rasilimali zilizowekewa mipaka, na miradi ya kawaida lazima ikatae baadhi ya mabadiliko yaliyopendekezwa, hivyo rasilimali zilizowekewa mipaka na kukataa mapendekezo sio ishara ya mradi usiotekelezwa.

    Mradi unapojua kwamba hautatengenezwa tena, unapaswa kuweka kigezo hiki kama "Haikidhi" na utumie utaratibu sahihi ili kuwaonyesha wengine kwamba hautengenezwi. Kwa mfano, tumia "DEPRECATED" kama kichwa cha kwanza cha README yake, ongeza "DEPRECATED" karibu na mwanzo wa ukurasa wake wa nyumbani, ongeza "DEPRECATED" mwanzoni mwa maelezo ya mradi wa hifadhi ya msimbo, ongeza nishani isiyolindwa katika README yake na/au ukurasa wa nyumbani, iweke kama iliyolemewa katika hifadhi yoyote ya kifurushi (k.m., npm deprecate), na/au utumie mfumo wa alama wa hifadhi ya msimbo ili kuihifadhi (k.m., mpangilio wa "archive" wa GitHub, alama ya "archived" ya GitLab, hali ya "readonly" ya Gerrit, au hali ya mradi wa "abandoned" wa SourceForge). Majadiliano ya ziada yanaweza kupatikana hapa.

    The project is under active development. Pull requests are being merged (for example #13 and #14 in November 2026), Dependabot updates are reviewed and landed, and release-please has opened the 1.0.0 release pull request (#2). SECURITY.md commits to acknowledging a vulnerability report within 3 working days and assessing it within 10.

    URL: https://github.com/ar27111994/maalik-e-makaan/pulls?q=is%3Apr


 Udhibiti wa Mabadiliko 9/9 ●

  • Hifadhi ya chanzo ya kudhibiti toleo ya hadharani


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na hifadhi ya chanzo ya kudhibiti toleo ambayo inaweza kusomwa hadharani na ina URL. [repo_public]
    URL YAWEZA kuwa sawa na URL ya mradi. Mradi YAWEZA kutumia matawi ya faragha (yasiyo ya umma) katika hali maalum wakati mabadiliko hayajatolewa hadharani (k.m., kwa kurekebisha udhaifu kabla haujafichuliwa kwa umma).

    The source is in a public Git repository on GitHub that anyone can read and clone without signing in. It holds the Flutter app, the Supabase migrations and Edge Functions, the Astro website, the formal models and the CI workflows.

    URL: https://github.com/ar27111994/maalik-e-makaan


    Ya kutosha kwa nishani!

    Hifadhi ya chanzo ya mradi LAZIMA ifuatilie mabadiliko yaliyofanywa, nani alifanya mabadiliko, na mabadiliko yalifanywa lini. [repo_track]

    Git records what changed, who made the change and when for every commit, and GitHub keeps the pull request, review and CI history for each one. After the initial commit, every change has reached main through a pull request. The project's convention is a squash merge with a Conventional Commit title, which commitlint checks in a lefthook commit-msg hook and in CI, and pr-title.yml checks the pull request title.

    URL: https://github.com/ar27111994/maalik-e-makaan/commits/main


    Ya kutosha kwa nishani!

    Ili kuwezesha ukaguzi wa ushirikiano, hifadhi ya chanzo ya mradi LAZIMA ijumuishe matoleo ya kati kwa ukaguzi kati ya matoleo; HAIPASWA kujumuisha matoleo ya mwisho tu. [repo_interim]
    Miradi YAWEZA kuchagua kuondoa matoleo maalum ya kati kutoka hifadhi zao za chanzo za umma (k.m., zile zinazorekebi udhaifu maalum usiokuwa wa umma, huenda zisitolewe hadharani, au zijumuishe nyenzo ambazo haziwezi kuwekwa kisheria na haziko katika toleo la mwisho).

    The repository holds work between releases, not only final releases. Every change is a public pull request whose individual commits and CI runs stay visible (PR #1 has 107 commits), and main already has several merged changes (#1, #13, #14) before the first release is cut by its own release pull request.

    URL: https://github.com/ar27111994/maalik-e-makaan/pull/1/commits


    Ya kutosha kwa nishani!

    INASHAURIWA kwamba programu ya kawaida ya udhibiti wa toleo iliyosambazwa itumike (k.m., git) kwa hifadhi ya chanzo ya mradi. [repo_distributed]
    Git haihitajiki kihususa na miradi inaweza kutumia programu ya udhibiti wa toleo iliyokusanyika (kama subversion) na sababu.

    The project uses Git, a distributed version control system, hosted on GitHub.

    URL: https://github.com/ar27111994/maalik-e-makaan


  • Unambari wa toleo wa kipekee


    Ya kutosha kwa nishani!

    Matokeo ya mradi LAZIMA yawe na kitambulisho cha kipekee cha toleo kwa kila toleo linalokusudiwa kutumiwa na watumiaji. [version_unique]
    Hii YAWEZA kukidhi kwa njia mbalimbali ikiwa ni pamoja na vitambulisho vya kuwasilisha (kama kitambulisho cha kuwasilisha cha git au kitambulisho cha seti ya mabadiliko cha mercurial) au nambari ya toleo (ikiwa ni pamoja na nambari za toleo zinazotumia uainishaji wa maana au mipango ya tarehe kama YYYYMMDD).

    Each release gets a unique version number, vX.Y.Z, from release-please, starting with v1.0.0. The release pull request writes the number into app/pubspec.yaml and website/package.json. The Release workflow builds with it (--build-name) and names each artefact with the tag, for example maalik-e-makaan-v1.0.0-web.zip.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/release-please-config.json


    Ya kutosha kwa nishani!

    INASHAURIWA kwamba muundo wa nambari ya toleo ya Semantic Versioning (SemVer) au Calendar Versioning (CalVer) itumike kwa matoleo. INASHAURIWA kwamba wale wanaotumia CalVer wajumuishe thamani ya kiwango cha mdogo. [version_semver]
    Miradi kwa ujumla inapaswa kupendelea muundo wowote unaotarajiwa na watumiaji wao, k.m., kwa sababu ni muundo wa kawaida unaotumiwa na ikolojia yao. Ikolojia nyingi zinapendelea SemVer, na SemVer kwa ujumla hupendelewa kwa kiolesura cha programu ya programu (API) na zana za maendeleo ya programu (SDK). CalVer hutumiwa na miradi ambayo ni kubwa, ina idadi kubwa ya utegemezi ulioundwa kwa uhuru, ina upeo wa mara kwa mara unaobadilika, au ni ya muda muhimu. INASHAURIWA kwamba wale wanaotumia CalVer wajumuishe thamani ya kiwango cha mdogo, kwa sababu kujumuisha kiwango cha mdogo kunasaidia matawi yaliyotunzwa kwa wakati mmoja wakati wowote hilo linakuwa lazima. Miundo mingine ya nambari ya toleo inaweza kutumiwa kama nambari za toleo, ikiwa ni pamoja na vitambulisho vya kuwasilisha cha git au vitambulisho vya seti ya mabadiliko cha mercurial, mradi tu vikitambulisha matoleo kwa kipekee. Hata hivyo, baadhi ya mbadala (kama vitambulisho vya kuwasilisha cha git) vinaweza kusababisha matatizo kama vitambulisho vya toleo, kwa sababu watumiaji huenda wasiwe na uwezo wa kuamua kwa urahisi ikiwa wako na toleo la hivi karibuni. Muundo wa kitambulisho cha toleo unaweza kutokuwa wa maana kwa kutambulisha matoleo ya programu ikiwa wapokeaji wote wanaendesha toleo la hivi karibuni tu (k.m., ni msimbo wa tovuti moja au huduma ya mtandao ambayo inasasishwa mara kwa mara kupitia utoaji wa kuendelea).

    Ya kutosha kwa nishani!

    INASHAURIWA kwamba miradi itambulishe kila toleo ndani ya mfumo wao wa udhibiti wa toleo. Kwa mfano, INASHAURIWA kwamba wale wanaotumia git watambulishe kila toleo kwa kutumia lebo za git. [version_tags]

    Each release is marked with a Git tag, vX.Y.Z (include-v-in-tag in release-please-config.json). Merging the release pull request creates the tag and the GitHub release, and the Release workflow builds and attaches that tag's artefacts with provenance attestations.

    URL: https://github.com/ar27111994/maalik-e-makaan/tags


  • Maelezo ya kutolewa


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe, katika kila toleo, maelezo ya toleo ambayo ni muhtasari unaosomeka na binadamu wa mabadiliko makuu katika toleo hilo ili kuwasaidia watumiaji kuamua ikiwa wanapaswa kusasisha na athari ya kusasisha itakuwa nini. Maelezo ya toleo LAZIMA yasiwe matokeo ghafi ya kumbukumbu ya udhibiti wa toleo (k.m., matokeo ya amri ya "git log" si maelezo ya toleo). Miradi ambayo matokeo yake hayakusudiwa kutumika tena katika maeneo mengi (kama programu kwa tovuti moja au huduma) NA wanaotumia utoaji wa kuendelea WAWEZA kuchagua "N/A". (URL inahitajika) [release_notes]
    Maelezo ya toleo YAWEZA kutekelezwa kwa njia mbalimbali. Miradi mingi hutoa katika faili inayoitwa "NEWS", "CHANGELOG", au "ChangeLog", kwa hiari na viendelezi kama ".txt", ".md", au ".html". Kihistoria neno "change log" lilimaanisha kumbukumbu ya kila mabadiliko, lakini ili kukidhi vigezo hivi kinachohitajika ni muhtasari unaosomeka na binadamu. Maelezo ya toleo YAWEZA badala yake kutolewa na taratibu za mfumo wa udhibiti wa toleo kama mtiririko wa Matoleo ya GitHub.

    Each release has human-readable release notes: release-please writes CHANGELOG.md and the GitHub release from Conventional Commit titles, grouped by kind. The v1.0.0 notes list the release's main features (portfolios and team roles, the rent ledger, receipts, caretakers, police registration, tax-year statements, WhatsApp reminders, the bilingual app and website).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/CHANGELOG.md


    Ya kutosha kwa nishani!

    Maelezo ya toleo LAZIMA yatambulishe kila udhaifu wa muda wa kutekeleza uliojulikana hadharani uliorekebishwa katika toleo hili ambao tayari ulikuwa na mgawanyo wa CVE au sawa wakati toleo lilipobuniwa. Kigezo hiki kinaweza kuwekwa alama kama haihusiki (N/A) ikiwa watumiaji kwa kawaida hawawezi kwa vitendo kusasisha programu wao wenyewe (k.m., kama inavyokuwa kweli mara nyingi kwa masasisho ya kernel). Kigezo hiki kinatumika tu kwa matokeo ya mradi, si kwa utegemezi wake. Ikiwa hakuna maelezo ya toleo au hakujawa na udhaifu uliojulikana hadharani, chagua N/A. [release_notes_vulns]
    Kigezo hiki kinawasaidia watumiaji kuamua ikiwa sasisho fulani litarekebisha udhaifu ambao unajulikana hadharani, ili kuwasaidia watumiaji kufanya uamuzi wa habari kuhusu kusasisha. Ikiwa watumiaji kwa kawaida hawawezi kwa vitendo kusasisha programu wao wenyewe kwenye kompyuta zao, lakini badala yake lazima wategemee wapatanishi mmoja au zaidi kutekeleza sasisho (kama inavyokuwa mara nyingi kwa kernel na programu ya kiwango cha chini ambayo imefungwa na kernel), mradi unaweza kuchagua "haihusiki" (N/A) badala yake, kwani habari hii ya ziada haitakuwa ya msaada kwa watumiaji hao. Vivyo hivyo, mradi unaweza kuchagua N/A ikiwa wapokeaji wote wanaendesha toleo la hivi karibuni tu (k.m., ni msimbo wa tovuti moja au huduma ya mtandao ambayo inasasishwa mara kwa mara kupitia utoaji wa kuendelea). Kigezo hiki kinatumika tu kwa matokeo ya mradi, si kwa utegemezi wake. Kuorodhesha udhaifu wa utegemezi wote wa mpito wa mradi unakuwa mgumu kadiri utegemezi unavyoongezeka na kutofautiana, na haihitajiki kwani zana zinazochunguza na kufuatilia utegemezi zinaweza kufanya hivi kwa njia inayopanuka.

    No publicly known run-time vulnerability has been fixed in the project's own code: it has no CVE assignments, and its list of GitHub security advisories is empty. Vulnerabilities are reported privately through GitHub security advisories (SECURITY.md). When a release fixes a published advisory, its release notes will name the GHSA or CVE ID.

    URL: https://github.com/ar27111994/maalik-e-makaan/security/policy


 Kuripoti 8/8 ●

  • Mchakato wa kuripoti hitilafu


    Ya kutosha kwa nishani!

    Mradi LAZIMA utoe mchakato kwa watumiaji kuwasilisha ripoti za hitilafu (k.m., kwa kutumia kifuatiliaji cha masuala au orodha ya barua pepe). (URL inahitajika) [report_process]

    Bugs are reported through GitHub Issues using a structured bug-report form (what happened, steps to reproduce, where it happened, app language, app version); blank issues are turned off so reporters are guided to the form. README.md (Contributing) and CONTRIBUTING.md (Reporting problems) point to the issue forms, and the website's privacy, terms and FAQ pages link to the issue tracker.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml


    Ya kutosha kwa nishani!

    Mradi UNAPASWA kutumia kifuatiliaji cha masuala kwa kufuatilia masuala ya mtu binafsi. [report_tracker]

    The project tracks individual issues in GitHub Issues, with bug-report and feature-request forms that apply the 'bug' and 'enhancement' labels automatically; pull requests are tracked in the same place.

    URL: https://github.com/ar27111994/maalik-e-makaan/issues


    Ya kutosha kwa nishani!

    Mradi LAZIMA uthibitishe wengi wa ripoti za hitilafu zilizowasilishwa katika miezi 2-12 iliyopita (ikiwemo); jibu halihitaji kuwa na marekebisho. [report_responses]

    The repository was created on 3 November 2026 and no bug reports have been filed yet: every item in the tracker so far is a pull request, so there are no unacknowledged reports. Bug reports come in through the bug-report form, which labels them 'bug', and the maintainer will acknowledge each one.

    URL: https://github.com/ar27111994/maalik-e-makaan/issues?q=is%3Aissue


    Ya kutosha kwa nishani!

    Mradi UNAPASWA kujibu wengi (>50%) wa maombi ya maboresho katika miezi 2-12 iliyopita (ikiwemo). [enhancement_responses]
    Jibu LIWEZA kuwa 'hapana' au majadiliano kuhusu manufaa yake. Lengo ni kwamba kuwe na jibu fulani kwa baadhi ya maombi, ambayo inaonyesha kwamba mradi bado unaishi. Kwa madhumuni ya kigezo hiki, miradi haihitaji kuhesabu maombi ya bandia (k.m., kutoka kwa wafanyabiashara haramu au mifumo ya kiotomatiki). Ikiwa mradi hauendelei kufanya maboresho tena, tafadhali chagua "haijatimizwa" na jumuisha URL inayofanya hali hii kuwa wazi kwa watumiaji. Ikiwa mradi huwa na msongo wa maombi ya maboresho, tafadhali chagua "haijatimizwa" na eleza.

    No enhancement requests have been filed since the repository was created on 3 November 2026, so none are waiting for a response. Requests come in through the feature-request form, which applies the 'enhancement' label, and the maintainer will respond to each one, even if the answer is no.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/ISSUE_TEMPLATE/feature_request.yml


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na kumbukumbu inayopatikana hadharani kwa ripoti na majibu kwa utaftaji wa baadaye. (URL inahitajika) [report_archive]

    All issues and pull requests, open and closed, with their comments, stay publicly available and searchable in the GitHub issue tracker of this public repository.

    URL: https://github.com/ar27111994/maalik-e-makaan/issues?q=


  • Mchakato wa kuripoti udhaifu


    Ya kutosha kwa nishani!

    Mradi LAZIMA uchapishe mchakato wa kuripoti udhaifu kwenye tovuti ya mradi. (URL inahitajika) [vulnerability_report_process]
    Miradi iliyohifadhiwa kwenye GitHub INAPASWA kuzingatia kuwezesha kuripoti udhaifu wa usalama kwa faragha. Miradi kwenye GitLab INAPASWA kuzingatia kutumia uwezo wake wa kuripoti udhaifu kwa faragha. Miradi YAWEZA kutambulisha anwani ya barua pepe kwenye https://PROJECTSITE/security, mara nyingi katika muundo wa security@example.org. Mchakato huu wa kuripoti udhaifu UWEZA kuwa sawa na mchakato wake wa kuripoti hitilafu. Ripoti za udhaifu ZIWEZA kuwa za umma kila wakati, lakini miradi mingi ina utaratibu wa kuripoti udhaifu wa faragha.

    SECURITY.md, which GitHub shows as the repository's security policy, explains how to report a vulnerability: privately through GitHub security advisories, never in a public issue. It also covers what to include, response times, supported versions, scope and safe harbour. CONTRIBUTING.md and the website's privacy page (English and Urdu) link to the policy, and the issue chooser sends security reports to the private advisory form.

    URL: https://github.com/ar27111994/maalik-e-makaan/security/policy


    Ya kutosha kwa nishani!

    Ikiwa ripoti za udhaifu wa faragha zinasaidiwa, mradi LAZIMA ujumuishe jinsi ya kutuma habari kwa njia ambayo inawekwa faragha. (URL inahitajika) [vulnerability_report_private]
    Mifano ni pamoja na ripoti ya kasoro ya faragha iliyowasilishwa kwenye wavuti kwa kutumia HTTPS (TLS) au barua pepe iliyosimbwa kwa kutumia OpenPGP. Ikiwa ripoti za udhaifu ni za umma kila wakati (kwa hiyo hakuna ripoti za udhaifu za faragha), chagua "haihusiki" (N/A).

    Private reports are supported: GitHub private vulnerability reporting is turned on for the repository, and SECURITY.md links directly to the private advisory form (security/advisories/new). Reports sent there go over HTTPS, and only the reporter and the repository's maintainers can see them. The issue chooser also sends security reports to this form, not to a public issue.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/SECURITY.md


    Ya kutosha kwa nishani!

    Muda wa majibu ya awali ya mradi kwa ripoti yoyote ya udhaifu iliyopokelewa katika miezi 6 iliyopita LAZIMA uwe chini ya au sawa na siku 14. [vulnerability_report_response]
    Ikiwa hakujawa na udhaifu ulioripotiwa katika miezi 6 iliyopita, chagua "haihusiki" (N/A).

    No vulnerability reports have been received in the last 6 months: the repository has no security advisories in any state (triage, draft, published or closed), and it dates from November 2026. SECURITY.md commits to acknowledging a report within 3 working days, well inside the 14-day limit.

    URL: https://github.com/ar27111994/maalik-e-makaan/security/advisories


 Ubora 13/13 ●

  • Mfumo wa ujenzi unaofanya kazi


    Ya kutosha kwa nishani!

    Ikiwa programu iliyotengenezwa na mradi inahitaji ujenzi wa matumizi, mradi LAZIMA utoe mfumo wa kujenga ambao unaweza kujenga programu kiotomatiki kutoka kwa chanzo-msimbo. [build]
    Mfumo wa kujenga huamua ni hatua gani zinahitaji kutendeka ili kujenga tena programu (na kwa mpangilio gani), na kisha kutekeleza hatua hizo. Kwa mfano, inaweza kuomba kikusanyaji kukusanya fumbo-chanzo. Ikiwa inayoweza kutekelezwa imeundwa kutoka kwa fumbo-chanzo, lazima iwezeshe marekebisho kwenye fumbo-chanzo ya mradi na kisha itengeneze msasisho inayoweza kutekelezwa na marekebisho hayo. Ikiwa programu iliyotolewa na mradi unategemea maktaba ya nje, mfumo wa kujenga haina haja ya kujenga maktaba hizo za nje. Ikiwa hakuna haja ya kujenga chochote kutumia programu baada ya fumbo-chanzo kubadilishwa, chagua "haitumiki" (N / A).

    Every deliverable is rebuilt from source by scripted commands: the root Makefile's make build-web-app (Flutter web release) and make build-apk (Android), npm run build in website/ (Astro), and flutter build ios for the unsigned iOS app. CI rebuilds all of them on every push and pull request (the web-build, android-build, ios-build and website jobs in ci.yml).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/Makefile


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kuwa zana za kawaida zitumike kujenga programu. [build_common_tools]
    Kwa mfano, Maven, Ant, cmake, autotools, make, rake (Ruby), au devtools (R).

    The build uses common, standard tools: GNU Make as the single entry point, the Flutter/Dart CLI for the app and packages, npm scripts with Astro for the website, and Deno tasks for the Edge Functions.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/Makefile


    Ya kutosha kwa nishani!

    Mradi UNAPASWA kujengwa kwa kutumia zana za FLOSS pekee yake. [build_floss_tools]

    The web app, website, Edge Functions, and database build and test with FLOSS tools only: Make, Flutter and Dart (BSD-3), Node, Astro, Deno, PostgreSQL and Python. Two native builds are exceptions. The Android APK uses Google's prebuilt Android SDK, which is released under Google's SDK licence, and the optional iOS build needs Apple's Xcode.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/CONTRIBUTING.md


  • Seti ya majaribio otomatiki


    Ya kutosha kwa nishani!

    Mradi LAZIMA utumie angalau seti moja ya majaribio ya kiotomatiki ambayo imetolewa hadharani kama FLOSS (seti hii ya majaribio inaweza kutunzwa kama mradi tofauti wa FLOSS). Mradi LAZIMA uonyeshe wazi au uandike jinsi ya kuendesha seti za majaribio (k.m., kupitia hati ya uingizaji wa kuendelea (CI) au kupitia nyaraka katika faili kama BUILD.md, README.md, au CONTRIBUTING.md). [test]
    Mradi YAWEZA kutumia seti nyingi za majaribio ya kiotomatiki (k.m., moja inayoendesha haraka, dhidi ya nyingine ambayo ni ya kina zaidi lakini inahitaji vifaa maalum). Kuna mifumo mingi ya majaribio na mifumo ya kusaidia majaribio inayopatikana, ikiwemo Selenium (uendeshaji kiotomatiki wa kivinjari cha wavuti), Junit (JVM, Java), RUnit (R), testthat (R).

    The repository includes its automated test suites under the MIT licence: Dart unit, widget and golden tests; 21 pgTAP database suites and concurrency scenarios; Deno Edge Function tests; Vitest and Playwright website tests; Playwright browser UAT; and Python tooling tests. README.md and CONTRIBUTING.md document Make test and the per-area targets, and ci.yml runs them.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/README.md


    Ya kutosha kwa nishani!

    Seti ya majaribio INAPASWA kuwa inaweza kuitwa kwa njia ya kawaida kwa lugha hiyo. [test_invocation]
    Kwa mfano, "make check", "mvn test", au "rake test" (Ruby).

    Make test runs every fast suite. Each area also has its own target (make test-core, test-app, test-db, test-functions, test-web, test-uat), and these targets call each language's standard runner (dart test, flutter test, deno task test, npm test with Vitest, python -m unittest).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/Makefile


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba seti ya majaribio ifuate wengi (au kwa kawaida wote) matawi ya msimbo, sehemu za kuingiza, na utendakazi. [test_most]

    Coverage gates in CI enforce high coverage: 100% line coverage for the mm_core domain library, 100% of lines, branches and functions for the Edge Functions, 95% of lines for the mm_ui design system and 90% for the app. Twenty-one pgTAP suites cover the database, including an RLS matrix and contract vectors shared with Dart. The website's Vitest and Playwright suites run in CI but have no numeric coverage gate.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/Makefile


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba mradi utekeleze ujumuishaji wendeleo (ambapo msimbo mpya au uliobadiishwa unajumuishwa mara kwa mara katika hifadhi ya msimbo ya kati na majaribio otomatiki hufanyika kwenye matokeo). [test_continuous_integration]

    GitHub Actions CI (ci.yml) runs on every push to main, on every pull request and in the merge queue. It runs formatting, linting, and analysis; every test suite with its coverage gate, pgTAP on PostgreSQL and on a full Supabase stack; Edge Function end-to-end tests; browser UAT; formal-model checks; and release builds. A single "CI passed" check, which needs every job, gates merges.

    URL: https://github.com/ar27111994/maalik-e-makaan/actions/workflows/ci.yml


  • Upimaji wa utendaji mpya


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na sera ya jumla (rasmi au la) kwamba utendakazi mkubwa mpya unavyoongezwa kwenye programu inayotengenezwa na mradi, majaribio ya utendakazi huo unapaswa kuongezwa kwenye seti ya majaribio otomatiki. [test_policy]
    Mradi uwe na sera tu, hata kwa maneno ya mdomo, inayosema wasanidi programu wanapaswa kuongeza majaribio kwenye seti ya majaribio otomatiki kwa utendakazi mkubwa mpya, chagua "Kukidhi."

    The policy is that new or changed functionality comes with automated tests. The pull request template requires "Tests cover the change, including edge cases and failure paths", and CONTRIBUTING.md requires pgTAP tests (and concurrency scenarios) for database changes. In the Dart packages, the app and the Edge Functions, CI's coverage gates also fail a change that adds code without tests.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/pull_request_template.md


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na ushahidi kwamba test_policy ya kuongeza majaribio imefuatwa katika mabadiliko makubwa ya hivi karibuni kwenye programu inayotengenezwa na mradi. [tests_are_added]
    Utendakazi mkubwa kawaida ungetajwa katika maelezo ya toleo. Ukamilifu hauhitajiki, ni ushahidi tu kwamba majaribio kawaida huongezwa kimakosa kwenye seti ya majaribio otomatiki utendakazi mkubwa mpya unavyoongezwa kwenye programu inayotengenezwa na mradi.

    Recent major changes added tests along with the code. The v1.0 pull request (#1) shipped the app, backend and website with their unit, widget, golden, pgTAP, Edge Function, website and UAT suites. The iOS packaging change (#14) added tool/ios/test_package_unsigned_ipa.py next to the new script and updated the UAT journeys.

    URL: https://github.com/ar27111994/maalik-e-makaan/pull/14


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba sera hii ya kuongeza majaribio (angalia test_policy) iwe imeandikwa katika maelekezo ya mapendekezo ya mabadiliko. [tests_documented_added]
    Hata hivyo, hata sheria isiyo rasmi inakubaliwa mradi majaribio yaongezwe kimakosa.

    Every change proposal fills in the pull request template, which says "Tests cover the change, including edge cases and failure paths". CONTRIBUTING.md requires pgTAP tests and concurrency scenarios for database changes, and docs/agents/workflows.md lists the tests to add for each kind of change.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/pull_request_template.md


  • Bendera za maonyo


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwashe bendera moja au zaidi za onyo la mkusanyaji, hali ya lugha "salama", au tumia zana tofauti ya "linter" kutafuta makosa ya ubora wa msimbo au makosa rahisi ya kawaida, ikiwa kuna angalau zana moja ya FLOSS inaweza kutekeleza kigezo hiki katika lugha iliyochaguliwa. [warnings]
    Mifano ya bendera za onyo la mkusanyaji ni pamoja na gcc/clang "-Wall". Mifano ya hali ya lugha "salama" ni pamoja na JavaScript "use strict" na perl5's "use warnings". Zana tofauti ya "linter" ni zana tu inayoangalia msimbo wa chanzo kutafuta makosa ya ubora wa msimbo au makosa rahisi ya kawaida. Hizi kawaida huwashwa ndani ya msimbo wa chanzo au maelekezo ya ujenzi.

    Each language has a linter or a strict mode enabled. Dart and Flutter use very_good_analysis with strict-casts, strict-inference and strict-raw-types. The website uses TypeScript (Astro's strictest config), ESLint (typescript-eslint strictTypeChecked, jsx-a11y) and Stylelint. Edge Functions use Deno strict mode and deno lint, Python uses ruff, shell uses shellcheck, workflows use actionlint and migrations use squawk.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/app/analysis_options.yaml


    Ya kutosha kwa nishani!

    Mradi LAZIMA ukabiliane na maonyo. [warnings_fixed]
    Haya ni maonyo yaliyotambuliwa na utekelezaji wa kigezo cha warnings. Mradi unapaswa kurekebisha maonyo au kuyaweka alama katika msimbo wa chanzo kama hasi za uwongo. Kwa kawaida pasingeweza kuwa na maonyo, lakini mradi YAWEZA kukubali baadhi ya maonyo (kawaida chini ya onyo 1 kwa mistari 100 au chini ya maonyo 10).

    Any warning fails CI, so warnings are fixed before a change merges: analyze --fatal-infos for Dart, --max-warnings=0 for ESLint and Stylelint, and deno lint, ruff and shellcheck all as gates. About 40 suppression comments are left outside generated code, each naming the specific rule and most giving a reason; 14 are reviewed squawk ignores in a single migration. ESLint reports unused disable directives as errors.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/ci.yml


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba miradi iwe na ukali mkubwa sana na maonyo katika programu inayotengenezwa na mradi, ambapo ni ya 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.

    The analysers run at maximum or near-maximum strictness. Info-level Dart diagnostics are fatal under very_good_analysis plus the strict language modes, and TypeScript uses Astro's strictest config with typescript-eslint strictTypeChecked and stylisticTypeChecked. Deno runs with strict and noUncheckedIndexedAccess plus extra lint rules (eqeqeq, no-non-null-assertion), and ruff enables bugbear, bandit security checks and other rule sets.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/website/eslint.config.js


 Usalama 16/16 ●

  • Maarifa ya maendeleo yenye usalama


    Ya kutosha kwa nishani!

    Mradi LAZIMA uwe na angalau msanidi mmoja mkuu anayejua jinsi ya kuunda programu salama. (Angalia 'maelezo' kwa mahitaji halisi.) [know_secure_design]
    Hii inahitaji kuelewa kanuni zifuatazo za muundo, ikiwa ni pamoja na kanuni 8 kutoka Saltzer na Schroeder:
    • uchumi wa utaratibu (weka muundo kuwa rahisi na mdogo iwezekanavyo, k.m., kwa kupitisha urahisishaji wa kufunga)
    • mipangilio ya kuzuia makosa (maamuzi ya kuingia yanapaswa kukataa kwa chaguo-msingi, na usakinishaji wa miradi unapaswa kuwa salama kwa chaguo-msingi)
    • kikuu cha kati kikamilifu (kuingia kote kunaweza kuwekwa kikomo lazima kufanyiwa ukaguzi wa mamlaka na kutowezesha kuvukwa)
    • muundo wazi (taratibu za usalama hazipaswi kutegemea ujinga wa mshambuliaji wa muundo wake, lakini badala yake kwenye habari iliyolindwa na kubadilishwa kwa urahisi kama funguo na nywila)
    • kutenganisha kwa upendeleo (kwa kawaida, ufikiaji kwa vitu muhimu unapaswa kutegemea zaidi ya sharti moja, ili kushinda mfumo mmoja wa ulinzi hautawasha ufikiaji kamili. K.m., uthibitishaji wa vipengele vingi, kama vile kuhitaji nywila na ishara za vifaa, ni imara zaidi kuliko uthibitishaji wa kipengele kimoja)
    • upendeleo mdogo zaidi (michakato inapaswa kufanya kazi na upendeleo mdogo zaidi unaohitajika)
    • utaratibu wa kawaida mdogo zaidi (muundo unapaswa kupunguza utaratibu wa kawaida kwa zaidi ya mtumiaji mmoja na kutegemewa na watumiaji wote, k.m., saraka za mafaili ya muda)
    • kukubalika kwa kisaikolojia (kiolesura cha binadamu lazima kiwe kimeundwa kwa urahisi wa matumizi - kuunda kwa "mshangao mdogo" kunaweza kusaidia)
    • uso wa shambulio uliowekewa mipaka (uso wa shambulio - seti ya sehemu tofauti ambapo mshambuliaji anaweza kujaribu kuingia au kutoa data - unapaswa kuwekwa mipaka)
    • uthibitishaji wa ingizo na orodha zinazokubalika (pembejeo kawaida zinapaswa kuangaliwa ili kuamua kama ni halali kabla ya kukubalika; uthibitishaji huu unapaswa kutumia orodha zinazokubalika (zinazokubali tu thamani zinazojulikana-nzuri), siyo orodha zinazokana (zinaozojaribu kuorodhesha thamani zinazojulikana-mbaya)).
    "Msanidi mkuu" katika mradi ni mtu yeyote ambaye anajua msingi wa msimbo wa mradi, ana faraja kufanya mabadiliko kwake, na anatambuliwa hivyo na washiriki wengine wengi katika mradi. Msanidi mkuu kawaida atafanya michango mingi kwa mwaka uliopita (kupitia msimbo, nyaraka, au kujibu maswali). Wasanidi kawaida wangeweza kuchukuliwa wasanidi wakuu ikiwa walianzisha mradi (na hawajatoka kwenye mradi zaidi ya miaka mitatu iliyopita), wana chaguo la kupokea habari kwenye kituo cha kuripoti udhaifu wa kibinafsi (ikiwa kuna), wanaweza kukubali ahadi kwa niaba ya mradi, au kufanya matoleo ya mwisho ya programu ya mradi. Ikiwa kuna msanidi mmoja tu, mtu huyo ndiye msanidi mkuu. Vitabu vingi na kozi zinapatikana kukusaidia kuelewa jinsi ya kuunda programu salama zaidi na kujadili muundo. Kwa mfano, kozi ya Misingi ya Maendeleo ya Programu Salama ni seti huru ya kozi tatu zinazoeleza jinsi ya kuunda programu salama zaidi (ni bure ukiifanyia ukaguzi; kwa ada ya ziada unaweza kupata cheti kuthibitisha ulijifunza nyenzo).

    The project's only developer is its primary developer, and the design is recorded in docs/architecture/permissions.md. All authorisation is enforced in one place, the database, so every request is checked whichever client sends it (economy of mechanism, complete mediation). Access is denied by default: every table has row-level security and the anon role holds no privilege on any relation, which pgTAP checks in supabase/tests/database/01_schema_security.test.sql (fail-safe defaults). Clients hold only the publishable key, and column grants keep system-owned columns unwritable (least privilege). Supabase Auth offers TOTP multi-factor sign-in (separation of privilege). Stored values and invitation tokens must match allowlist formats (CHECK constraints and regular expressions). The design is public and depends only on keys and per-invitation random secrets (open design).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/docs/architecture/permissions.md


    Ya kutosha kwa nishani!

    Angalau mmoja wa wasanidi wakuu wa mradi LAZIMA wajue aina za kawaida za makosa ambayo husababisha udhaifu katika aina hii ya programu, pamoja na angalau mbinu moja ya kukabiliana au kupunguza kila moja. [know_common_errors]
    Mifano (kulingana na aina ya programu) ni pamoja na uvamizi wa SQL, uvamizi wa OS, mtiririko wa kipengele cha kawaida, uandishi wa tovuti-tofauti, uthibitishaji unaokosekana, na uidhinishaji unaokosekana. Angalia CWE/SANS top 25 au OWASP Top 10 kwa orodha zinazotumika kawaida. Vitabu vingi na kozi zinapatikana kukusaidia kuelewa jinsi ya kuunda programu salama zaidi na kujadili makosa ya kawaida ya utekelezaji ambayo husababisha udhaifu. Kwa mfano, kozi ya Misingi ya Maendeleo ya Programu Salama ni seti huru ya kozi tatu zinazoeleza jinsi ya kuunda programu salama zaidi (ni bure ukiifanyia ukaguzi; kwa ada ya ziada unaweza kupata cheti kuthibitisha ulijifunza nyenzo).

    The project counters the common errors for a web and mobile app on a database API, as its code and docs show. Missing authorisation: row-level security on every table, tested by the pgTAP RLS matrix (03_rls_matrix.test.sql). SQL injection: parameterised PostgREST and RPC calls, and every function pins search_path. Cross-site scripting: a strict Content-Security-Policy without inline scripts (website/vercel.json, docs/operations.md). Leaked secrets: the app refuses a secret key, and gitleaks scans the history in CI. Timing attacks: tokens are compared in constant time. Brute force: rate limits per user and per action. CSV formula injection: exported cells are guarded (app/lib/src/features/insights/presentation/csv.dart). CodeQL runs its security-and-quality queries on every change.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/SECURITY.md


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

    Programu iliyotengenezwa na mradi LAZIMA itumie, kwa chaguo-msingi, tu itifaki za kriptografia na mifumbo ambazo zimechapishwa hadharani na kukaguliwa na wataalam (ikiwa itifaki za kriptografia na mafumbo imetumika). [crypto_published]
    Vigezo hivi vya kriptografia mara mingi havitumiki kwa sababu programu zingine hazina haja ya kutumia moja kwa moja uwezo wa kriptografia.

    The project uses only published algorithms and protocols that experts have reviewed. These are SHA-256 and HMAC-SHA-256 through Web Crypto in the Edge Functions (supabase/functions/_shared/crypto.ts), PostgreSQL's built-in sha256() and pgcrypto's gen_random_bytes in the database, and bcrypt in Supabase Auth. JWTs are checked against the project's JWKS by Supabase's own library (@supabase/server). All transport is TLS (HTTPS), provided by Supabase and Vercel.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/functions/_shared/crypto.ts


    Ya kutosha kwa nishani!

    Ikiwa programu iliyotengenezwa na mradi ni programu au maktaba, na kusudi lake la msingi sio kutekeleza usimbuaji, basi INAPASWA tu kuita programu iliyoundwa kihususa kutekeleza kazi za kielelezo; HAIPASWI kutekeleza-upya shughuli hiyo. [crypto_call]

    The project implements no cryptographic primitive of its own. It calls Web Crypto (crypto.subtle) in the Edge Functions and PostgreSQL's sha256() and pgcrypto's gen_random_bytes in the database. Its own crypto-related code is only a constant-time comparison of digests. Passwords, sessions and JWT signing are handled by Supabase Auth, and TLS by Supabase and Vercel.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/functions/_shared/crypto.ts


    Ya kutosha kwa nishani!

    Utendaji wote katika programu iliyotengenezwa na mradi ambayo inategemea usimbuaji LAZIMA iweze kutekelezwa kwa kutumia FLOSS. [crypto_floss]
    Tazama Mahitaji ya Viwango wazi ya Programu kupitia Open Source Initiative.

    Everything that depends on cryptography is free and open-source software. That includes Deno's Web Crypto, PostgreSQL with pgcrypto, Supabase Auth (GoTrue, MIT licence) with bcrypt, the Dart SDK, age for encrypted backups, and standard TLS. No proprietary or patent-encumbered algorithm is needed.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/functions/_shared/crypto.ts


    Ya kutosha kwa nishani!

    Mifumo ya usalama ndani ya programu inayozalishwa na mradi LAZIMA itumie kwa msingi keylengths ambazo angalau zinakidhi mahitaji ya chini ya NIST kufikia mwaka wa 2030 (kama ilivyoelezwa mnamo 2012). LAZIMA iwe rahisi kusanidi programu ili keylengths ndogo zimezimwa kabisa. [crypto_keylength]
    Vipimo hivi vya urefu wa charaza ni: symmetric key 112, factoring modulus 2048, discrete logarithm key 224, discrete logarithmic group 2048, elliptic curve 224, na hash 224 (ufichuzi wa nywila haujashughulikiwa kwenye urefu wa charaza hii, maelezo zaidi ya ufichuzi wa nywila yanapatikana ndani ya kigezo cha crypto_password_storage). Ona https://www.keylength.com kwa mliganisho wa mapendekezo ya funguo-refu kutoka mashirika mbali mbali. Programu YAWEZA kubali funguo-refu ndogo katika usanidi (haifai kukubali, maana hii huwacha mashambulizi ya kushusha, lakini funguo-refu fupi wakati mwingine ina manufaa ya upatanifu).

    The project's own mechanisms use fixed sizes above the NIST 2030 minimums, and none can be set smaller. Invitation secrets are 256 random bits from gen_random_bytes(32), stored as SHA-256 (supabase/migrations/20261108082804_invitation_findings.sql). Comparisons and digests use HMAC-SHA-256 and SHA-256. The Edge Functions refuse an operator-set bearer token shorter than 32 characters (MIN_TOKEN_LENGTH in supabase/functions/_shared/config.ts). TLS and JWT signing keys are managed by Supabase and Vercel.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/migrations/20261108082804_invitation_findings.sql


    Ya kutosha kwa nishani!

    Mifumo ya usalama ya chaguo-msingi ndani ya programu inayozalishwa na mradi LAZIMA ISITEGEMEE algoriti zilizovunjika za kriptologia (k.m., MD4, MD5, DES moja, RC4, Dual_EC_DRBG), au kutumia hali za cipher ambazo si sahihi kwa muktadha, isipokuwa ni muhimu kutekeleza itifaki inayoweza kushirikiana (ambapo itifaki iliyotekelezwa ni toleo la hivi karibuni zaidi la kiwango hicho kinachotegemeana sana na mfumo wa mtandao, mfumo huo unahitaji matumizi ya algoriti au hali hiyo, na mfumo huo haupatii chaguo lolote salama zaidi). Nyaraka LAZIMA zieleze hatari zozote za usalama husika na upungufu wowote unaojulikana ikiwa algoriti hizi zilizovunjika au hali ni muhimu kwa itifaki inayoweza kushirikiana. [crypto_working]
    Hali ya ECB ni karibu kamwe haifai kwa sababu inaonyesha block zinazofanana ndani ya ciphertext kama ilivyoonyeshwa na penguin wa ECB, na hali ya CTR mara nyingi si sahihi kwa sababu haifanyi uthibitishaji na husababisha nakala ikiwa hali ya ingizo inarudiwa. Katika hali nyingi ni bora kuchagua hali ya algoriti ya block cipher iliyoundwa kuchanganya siri na uthibitishaji, k.m., Galois/Counter Mode (GCM) na EAX. Miradi YAWEZA kuwaruhusu watumiaji kuwasha taratibu zilizovunjika (k.m., wakati wa usanidi) ambapo ni muhimu kwa upatanifu, lakini hapo watumiaji wanajua wanafanya hivyo.

    No security mechanism uses MD4, MD5, single DES, RC4, Dual_EC_DRBG or an unsuitable cipher mode. Hashes are SHA-256 and MACs are HMAC-SHA-256. The backup workflow (.github/workflows/backup.yml) encrypts with age, which uses ChaCha20-Poly1305 authenticated encryption. MD5 appears only in tool/db/schema_fingerprint.sql, which compares schema definitions to detect drift. It is not a security control.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/functions/_shared/crypto.ts


    Ya kutosha kwa nishani!

    Mifumo ya usalama ya chaguo-msingi ndani ya programu inayozalishwa na mradi INAPASWA 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.

    The default mechanisms use neither SHA-1 nor CBC mode in SSH. They use SHA-256, HMAC-SHA-256 and 256-bit random secrets, age (ChaCha20-Poly1305) for encrypted backups; and the TLS provided by Supabase and Vercel.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/functions/_shared/crypto.ts


    Ya kutosha kwa nishani!

    Mifumo ya usalama ndani ya programu iliyotengenezwa na mradi INAPASWA kutekeleza kwa ukamilifu usiri wa umbele ya itifaki za makubaliano ya funguo ili funguo la kipindi kilicho tokana na kikao cha vifungo muda-mrefu haziwezi kuridhi mabaya ikiwa mojawapo ya vifunguo vya muda-mrefu imeridhi mabaya katika usoni. [crypto_pfs]

    The software implements no key-agreement protocol of its own. All traffic is HTTPS, terminated by Vercel (website and web app) and Supabase (API, Auth, Storage). The app refuses a Supabase or app URL that is not HTTPS, except for loopback addresses in local development (app/lib/src/config/app_config.dart).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/app/lib/src/config/app_config.dart


    Ya kutosha kwa nishani!

    Ikiwa programu iliyotengenezwa na mradi imesababisha uhifadhi wa nywila kwa minajili ya uthibitishaji ya watumiaji wa kutoka nje, nywila LAZIMA zihifadhiwe kwa mficho uliorudiarudia na chumvi kwa kila-mtumiaji kwa kutumia kanuni ya upanuaji (rudiarudia) wa funguo (k.m., Argon2id, Bcrypt, Scrypt, or PBKDF2). Ona pia Kurasadogo ya Uhifadhi wa Nywila la OWASP). [crypto_password_storage]
    Kigezo hili linatumika tu wakati programu linatekeleza uthibitishaji wa watumiaji kutumia nywila kwa watumiaji wa nje (ambayo pia ni uthibitishaji unaelekezwa ndani), kama vile programu za tovuti zinazobakia seva). Haitumiki katika visa ambavyo programu inahifadhi nywila ili kudhibitisha ndani ya mifumo mingine (ambayo pia ni ithibitishaji unaelekezwa nje, k.m., programu inatekeleza teja la mfumo lingineyo), maana angalau sehemu za programu lazima ziwe na njia ya kupata hiyo nywila isigalifichwa.

    The project does not hash passwords itself. Sign-in uses Supabase Auth (GoTrue), which stores each password as a bcrypt hash with a per-user salt. supabase/config.toml requires passwords of at least 10 characters with upper-case and lower-case letters and digits, and enables TOTP multi-factor authentication. The local demo seed also stores its demo password with crypt(..., gen_salt('bf')).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/config.toml


    Ya kutosha kwa nishani!

    Mifumo ya usalama ndani ya programu iliyotengenezwa na mradi LAZIMA itoe funguo zote za kriptologia na nonces kwa kutumia kitengeneza cha nambari za bahati kuptia kriptologia salama, na ISIWEZE kufanya hivo kutumia vitengenezi zisizo salama kikriptologia. [crypto_random]
    Kitengeneza cha nambari za bahati nasibu za kriptologia salama kinaweza kuwa kitengeneza cha nambari za bahati nasibu za vifaa, au kinaweza kuwa kitengeneza cha nambari za bahati nasibu za kriptologia salama (CSPRNG) kwa kutumia algoriti kama vile Hash_DRBG, HMAC_DRBG, CTR_DRBG, Yarrow, au Fortuna. Mifano ya simu kwa vitengeneza cha nambari za bahati nasibu salama ni pamoja na java.security.SecureRandom ya Java na window.crypto.getRandomValues ya JavaScript. Mifano ya simu kwa vitengeneza cha nambari za bahati nasibu zisizo salama ni pamoja na java.util.Random ya Java na Math.random ya JavaScript.

    Every secret is generated by a cryptographically secure generator. Invitation verifiers come from pgcrypto's gen_random_bytes(32), and the Edge Functions create HMAC keys with crypto.subtle.generateKey. Identifiers are also drawn from secure sources: Dart's Random.secure in the app (app/lib/src/data/ids.dart) and crypto.randomUUID or gen_random_uuid elsewhere. Seeded Random appears only in tests, and Math.random only in a browser test script, where it makes up a path that does not exist.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/migrations/20261108082804_invitation_findings.sql


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


    Ya kutosha kwa nishani!

    Mradi LAZIMA utumie utaratibu wa utoaji ambao unakabiliana na mashambulizi ya MITM. Kutumia https au ssh+scp ni inakubaliwa. [delivery_mitm]
    Utaratibu wenye nguvu zaidi ni kutoa programu na vifurushi vilivyosainiwa kidigitali, kwa kuwa hiyo inapunguza mashambulizi kwenye mfumo wa usambazaji, lakini hii inafanya kazi tu ikiwa watumiaji wanaweza kuwa na uhakika kwamba funguo za umma kwa saini ni sahihi na ikiwa watumiaji watakagua saini kweli kweli.

    GitHub delivers the source over HTTPS or SSH. The website and web app are served over HTTPS on Vercel with HSTS (website/vercel.json, tool/web/package_vercel.py). For each release, starting with v1.0.0, release.yml uploads the builds to GitHub Releases over HTTPS. It adds a SHA256SUMS file and a Sigstore-signed build provenance attestation (actions/attest-build-provenance), which gh attestation verify can check.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/release.yml


    Ya kutosha kwa nishani!

    Hash ya kriptologia (k.m., sha1sum) LAZIMA ISICHUKULIWE kupitia http na kutumika bila kuangalia saini ya kriptologia. [delivery_unsigned]
    Hash hizi zinaweza kurekebishwa wakati wa usafiri.

    No hash is fetched over plain HTTP. Checksums for downloaded tools are pinned in the repository and checked after an HTTPS download: gitleaks in security.yml, and the formal toolchain in tool/formal/install.sh, which uses curl --proto '=https' --tlsv1.2. Release SHA256SUMS files are served over HTTPS next to a signed provenance attestation.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/security.yml


  • Udhaifu uliofahamika hadharani umeshughulikiwa


    Ya kutosha kwa nishani!

    LAZIMA kuwe hakuna udhaifu usiorekebishwa wa kiwango cha kati au juu zaidi ambao umejulikana hadharani kwa zaidi ya siku 60. [vulnerabilities_fixed_60_days]
    Udhaifu lazima urekebishwe na kutolewa na mradi wenyewe (rekebisho zinaweza kutengenezwa mahali pengine). Udhaifu unakuwa unajulikana hadharani (kwa kusudi hili) mara tu unapata CVE yenye taarifa zilizotolewa hadharani zisizolipwa (zilizoripotiwa, kwa mfano, katika Hifadhidata ya Taifa ya Udhaifu) au wakati mradi umefahamishwa na taarifa imetolewa kwa umma (labda na mradi). Udhaifu unazingatiwa kuwa wa kiwango cha kati au juu ikiwa alama yake ya Common Vulnerability Scoring System (CVSS) ya msingi ya ubora ni kati au juu. Katika matoleo ya CVSS 2.0 hadi 3.1, hii ni sawa na alama ya CVSS ya 4.0 au zaidi. Miradi inaweza kutumia alama ya CVSS kama ilivyochapishwa katika hifadhidata ya udhaifu inayotumika sana (kama vile Hifadhidata ya Taifa ya Udhaifu) kwa kutumia toleo la hivi karibuni la CVSS lililoripotiwa katika hifadhidata hiyo. Miradi badala yake inaweza kuhesabu ukali wao wenyewe kwa kutumia toleo la hivi karibuni la CVSS wakati wa ufunuzi wa udhaifu, ikiwa ingizo la hesabu linatangazwa hadharani mara tu udhaifu unajulikana hadharani. Kumbuka: hii inamaanisha kwamba watumiaji wanaweza kuachwa katika hatari kwa washambuliaji wote duniani kwa siku hadi 60. Kigezo hiki ni rahisi zaidi kukidhi kuliko yale Google inapendekeza katika Rebooting responsible disclosure, kwa sababu Google inapendekeza kwamba kipindi cha siku 60 kianze wakati mradi unafahamishwa hata ikiwa ripoti si ya umma. Pia kumbuka kwamba kigezo hiki cha nishani, kama vigezo vingine, kinatumika kwa mradi wa mtu binafsi. Baadhi ya miradi ni sehemu ya mashirika makubwa ya mwavuli au miradi mikubwa, labda katika safu nyingi, na miradi mingi inatoa matokeo yao kwa mashirika mengine na miradi kama sehemu ya mnyororo wa usambazaji wenye utata. Mradi wa mtu binafsi mara nyingi hauwezi kudhibiti wengine, lakini mradi wa mtu binafsi unaweza kufanya kazi kutoa rekebisho ya udhaifu kwa wakati. Kwa hiyo, tunazingatia tu muda wa jibu wa mradi wa mtu binafsi. Mara tu rekebisho inapatikana kutoka kwa mradi wa mtu binafsi, wengine wanaweza kuamua jinsi ya kushughulikia rekebisho (k.m., wanaweza kusasisha kwenye toleo jipya au wanaweza kutumia rekebisho tu kama suluhisho lililochaguliwa-cherry).

    No vulnerability has been reported or published against the project: it has no security advisories and no CVEs, and the repository is less than 60 days old (first commit on 3 November 2026). Private vulnerability reporting is enabled. OSV-Scanner checks every lockfile on each change and weekly; Dependabot keeps dependencies current, and the Security workflow passes on main.

    URL: https://github.com/ar27111994/maalik-e-makaan/security/policy


    Ya kutosha kwa nishani!

    Miradi INAPASWA kurekebisha udhaifu wote muhimu haraka baada ya kuripotiwa. [vulnerabilities_critical_fixed]

    SECURITY.md commits to acknowledging a report within 3 working days and assessing its severity within 10 working days. It also says confirmed issues are fixed before anything else, and that only the latest release and main receive fixes. No critical vulnerability has been reported so far.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/SECURITY.md


  • Masuala mengine ya usalama


    Ya kutosha kwa nishani!

    Hazina za umma LAZIMA ZISIVUJE uthibitisho halali wa faragha (k.m., nywila inayofanya kazi au funguo ya faragha) ambayo imekusudiwa kupunguza upatikanaji wa umma. [no_leaked_credentials]
    Mradi UNAWEZA kuvuja uthibitisho wa "sampuli" kwa majaribio na hifadhidata zisizo muhimu, mradi tu hazikusudiwa kupunguza upatikanaji wa umma.

    The repository contains no working credential. Gitleaks scans the whole history on every change (security.yml). Its allowlist (.gitleaks.toml) admits only three named fake test-fixture values, and only inside test directories. The only other credential is the demo password in supabase/seed.sql, which is for local development and CI only and is never applied to the hosted project. Real secrets live in the GitHub, Supabase and Vercel secret stores. The two committed .env.example files hold only URLs, no secrets.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.gitleaks.toml


 Uchanganuzi 8/8 ●

  • Uchambuzi tuli wa msimbo


    Ya kutosha kwa nishani!

    Angalau zana moja ya uchambuzi wa msimbo tuli (zaidi ya maonyo ya mkusanyaji na hali za lugha "salama") LAZIMA itumike kwa toleo lolote lililopendekezwa kubwa la uzalishaji wa programu kabla ya toleo lake, ikiwa kuna angalau zana moja ya FLOSS inayotekeleza kigezo hiki katika lugha iliyochaguliwa. [static_analysis]
    Zana ya uchambuzi wa msimbo tuli inachunguza msimbo wa programu (kama msimbo wa chanzo, msimbo wa kati, au utekelezaji) bila kuutekeleza na ingizo maalum. Kwa madhumuni ya kigezo hiki, maonyo ya mkusanyaji na hali za lugha "salama" hazihesabiwi kama zana za uchambuzi wa msimbo tuli (hizi kwa kawaida huepuka uchambuzi wa kina kwa sababu kasi ni muhimu). Baadhi ya zana za uchambuzi wa msimbo tuli zinazingatia kugundua hitilafu za jumla, nyingine zinazingatia kupata aina fulani za hitilafu (kama vile udhaifu), na baadhi hufanya mchanganyiko. Mifano ya zana hizo za uchambuzi wa msimbo tuli ni pamoja na cppcheck (C, C++), clang static analyzer (C, C++), SpotBugs (Java), FindBugs (Java) (ikiwa ni pamoja na FindSecurityBugs), PMD (Java), Brakeman (Ruby on Rails), lintr (R), goodpractice (R), Coverity Quality Analyzer, SonarQube, Codacy, na HP Enterprise Fortify Static Code Analyzer. Orodha kubwa za zana zinaweza kupatikana katika maeneo kama vile orodha ya Wikipedia ya zana za uchambuzi wa msimbo tuli, taarifa za OWASP kuhusu uchambuzi wa msimbo tuli, orodha ya NIST ya vichambua usalama wa msimbo wa chanzo, na orodha ya Wheeler ya zana za uchambuzi tuli. Ikiwa hakuna zana za uchambuzi tuli za FLOSS zinazopatikana kwa lugha za utekelezaji zilizotumika, unaweza kuchagua 'N/A'.

    Every pull request and every push to main runs CodeQL with the security-and-quality queries on the TypeScript/JavaScript (website and Edge Functions) and on the GitHub Actions workflows, and zizmor on the workflows (.github/workflows/security.yml), so the commit each release is tagged from has been analysed. CI also runs the Dart analyzer with very_good_analysis and --fatal-infos, deno lint, ESLint with typescript-eslint strictTypeChecked and --max-warnings=0, plpgsql_check (supabase db lint --fail-on error), squawk on new migrations, ruff, shellcheck and actionlint (.github/workflows/ci.yml; Makefile targets analyze and lint). Dart has no CodeQL extractor, so the Dart code is covered by the analyzer rules and the tests.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/security.yml


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba angalau moja ya zana za uchambuzi tuli zilizotumika kwa kigezo cha static_analysis ijumuishe sheria au njia za kutafuta udhaifu wa kawaida katika lugha au mazingira yaliyochambuliwa. [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'.

    CodeQL runs its security-and-quality query suite, which includes the security (CWE) queries for JavaScript/TypeScript, such as injection and cross-site scripting, and for GitHub Actions, such as code injection and untrusted checkout. Zizmor audits the workflows for known Actions vulnerability patterns, and Gitleaks scans the whole Git history for leaked secrets (.github/workflows/security.yml).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/security.yml


    Ya kutosha kwa nishani!

    Udhaifu wote wenye ukali wa kati na juu zaidi unaoweza kudhoofishwa uliogundulika kupitia uchambuzi wa msimbo tuli LAZIMA urekebishwe kwa wakati baada ya kuthibitishwa. [static_analysis_fixed]
    Udhaifu unazingatiwa kuwa wa kiwango cha kati au juu zaidi ikiwa alama yake ya Common Vulnerability Scoring System (CVSS) ya msingi ya ubora ni kati au juu. Katika matoleo ya CVSS 2.0 hadi 3.1, hii ni sawa na alama ya CVSS ya 4.0 au zaidi. Miradi inaweza kutumia alama ya CVSS kama ilivyochapishwa katika hifadhidata ya udhaifu inayotumika sana (kama vile Hifadhidata ya Taifa ya Udhaifu) kwa kutumia toleo la hivi karibuni la CVSS lililoripotiwa katika hifadhidata hiyo. Miradi badala yake inaweza kuhesabu ukali wao wenyewe kwa kutumia toleo la hivi karibuni la CVSS wakati wa ufunuzi wa udhaifu, ikiwa ingizo la hesabu linatangazwa hadharani mara tu udhaifu unajulikana hadharani. Kumbuka kwamba kigezo cha vulnerabilities_fixed_60_days kinahitaji kwamba udhaifu wote kama huo urekebishwe ndani ya siku 60 baada ya kuwa wa umma.

    CodeQL and zizmor send their results to GitHub code scanning on every pull request and push to main, and the CI analyzers block merging on any finding through the required "CI passed" check (--fatal-infos, --max-warnings=0, plpgsql_check --fail-on error). Confirmed security issues are fixed before other work, as SECURITY.md says, and no medium or higher static-analysis finding is open.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/security.yml


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba uchambuzi wa msimbo wa chanzo tuli ufanyike kwenye kila ahadi au angalau kila siku. [static_analysis_often]

    The Security workflow (CodeQL, zizmor, gitleaks, OSV-Scanner) runs on every push to main, on every pull request and weekly on a schedule (.github/workflows/security.yml). The CI workflow runs the analyzers and linters on every pull request and every push to main, and "CI passed" is the required check for merging (.github/workflows/ci.yml).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/security.yml


  • Uchambuzi wa msimbo wa nguvu za ziada


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba angalau zana moja ya uchambuzi wa nguvu itumike kwenye toleo kubwa lolote la uzalishaji lililopendekezwa la programu 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.

    CI runs on every pull request and every push to main, so before each release it runs test suites that execute the code with varied inputs. The Edge Function tests must reach 100% line, branch and function coverage (make test-functions). Seeded randomised property tests run thousands of cases on the money and rent arithmetic in mm_core (money_test.dart, allocation_test.dart) and on the website (tests/unit/money.test.ts, rent-math.test.ts). tool/db/concurrency_test.sh runs 30 parallel race scenarios on real PostgreSQL and then checks the ledger and ownership invariants. Playwright UAT takes the built web app through every user journey on a local Supabase stack, and the website's Playwright tests run axe. fast-check property tests are being added to the website.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/tool/db/concurrency_test.sh


    Ya kutosha kwa nishani!

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

    The software the project releases is written in memory-safe languages: Dart (the app and packages), TypeScript (the Edge Functions and website) and SQL/PL/pgSQL, with small amounts of Kotlin and Swift platform glue. The only C/C++ in the repository is Flutter's generated Linux desktop runners (app/linux/runner and packages/mm_ui/example/linux/runner), which are used only to run tests locally and are never built for release. Releases contain only the Android, iOS and web builds (.github/workflows/release.yml).

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/.github/workflows/release.yml


    Ya kutosha kwa nishani!

    INAPENDEKEZWA kwamba mradi utumie usanidi wa angalau baadhi ya uchambuzi wa nguvu (kama vile majaribio au fuzzing) ambao huwezesha madai mengi. Katika hali nyingi madai haya yasipaswi kuwa yamewezeshwa katika mijengo ya uzalishaji. [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.

    The Dart and Flutter tests (dart test, flutter test in the Makefile) run in debug mode with assertions on. This enables the assert() checks in mm_ui and the app, and Flutter's own framework assertions, and release builds strip them. mm_core checks its arguments with exceptions that are always on (ArgumentError). Each scenario in tool/db/concurrency_test.sh checks its own expected outcome, and the run ends by checking the ledger and ownership invariants.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/Makefile


    Ya kutosha kwa nishani!

    Udhaifu wote wenye ukali wa kati na juu zaidi unaoweza kudhoofishwa uliogundulika kupitia uchambuzi wa msimbo wa nguvu LAZIMA urekebishwe kwa wakati baada ya kuthibitishwa. [dynamic_analysis_fixed]
    Ikiwa haujafanya uchambuzi wa msimbo wa nguvu na kwa hivyo hukupata udhaifu wowote kwa njia hii, chagua "haihusiki" (N/A). Udhaifu unazingatiwa kuwa wa kiwango cha kati au juu zaidi ikiwa alama yake ya Common Vulnerability Scoring System (CVSS) ya msingi ya ubora ni kati au juu. Katika matoleo ya CVSS 2.0 hadi 3.1, hii ni sawa na alama ya CVSS ya 4.0 au zaidi. Miradi inaweza kutumia alama ya CVSS kama ilivyochapishwa katika hifadhidata ya udhaifu inayotumika sana (kama vile Hifadhidata ya Taifa ya Udhaifu) kwa kutumia toleo la hivi karibuni la CVSS lililoripotiwa katika hifadhidata hiyo. Miradi badala yake inaweza kuhesabu ukali wao wenyewe kwa kutumia toleo la hivi karibuni la CVSS wakati wa ufunuzi wa udhaifu, ikiwa ingizo la hesabu linatangazwa hadharani mara tu udhaifu unajulikana hadharani.

    No medium or higher exploitable vulnerability found by dynamic analysis is open. A failing test blocks merging through the required "CI passed" check. Races found before 1.0.0 were fixed by new migrations, for example, supabase/migrations/20261105170557_concurrency_findings.sql (a race could leave a document without its file, and writes are now authorised again after taking the lock). Each fix has a regression scenario in tool/db/concurrency_test.sh that fails without it.

    URL: https://github.com/ar27111994/maalik-e-makaan/blob/main/supabase/migrations/20261105170557_concurrency_findings.sql



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

Ingizo la nishani ya mradi linamilikiwa na: Ahmed Rehan.
Ingizo liliundwa siku 2026-11-09 16:41:37 UTC, iliyosasishwa mara ya mwisho siku 2026-11-09 18:17:32 UTC. Ilipata mara ya mwisho nishani ya kupita siku 2026-11-09 18:17:32 UTC.