podtrace

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


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

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

        

 Misingi 15/17 ●

  • Jumla

    Kumbuka kwamba miradi mingine inaweza kutumia jina sawa.

    eBPF-driven diagnostic tool for Kubernetes applications 🐝

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

  • Mahitaji ya awali


    Ya kutosha kwa nishani!

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

  • Maudhui ya kimsingi ya tovuti ya mradi


    Ya kutosha kwa nishani!

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

    https://github.com/gma1k/podtrace/blob/main/CONTRIBUTING.md


  • Usimamizi wa mradi


    Ya kutosha kwa nishani!

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

    Podtrace uses the Developer Certificate of Origin (DCO), not a CLA or CAA.

    Policy and explanation: https://github.com/gma1k/podtrace/blob/main/CONTRIBUTING.md#developer-certificate-of-origin
    The section links to https://developercertificate.org/ and states what signing off means for this project: the contributor asserts they wrote the code or have the right to submit it under Apache-2.0, that they have employer permission where the employer owns the copyright, and that the name and email in the trailer are public and permanent. Contributors add the trailer with git commit -s.

    Enforcement: https://github.com/gma1k/podtrace/blob/main/.github/workflows/dco.yml
    The workflow runs on every pull request and verifies that each commit in the PR carries a Signed-off-by: trailer whose email matches the commit author's email. Missing sign-offs fail the check and block the merge. Machine-generated commits from bot accounts (renovate, dependabot, github-actions) are exempt, since a bot cannot make the DCO assertion.

    Contributors are also reminded in the pull request template: https://github.com/gma1k/podtrace/blob/main/.github/PULL_REQUEST_TEMPLATE.md


    Ya kutosha kwa nishani!

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

    Podtrace documents a maintainer-led governance model in GOVERNANCE.md:
    https://github.com/gma1k/podtrace/blob/main/GOVERNANCE.md

    Roles: the document defines Contributors (anyone opening an issue, answering in Discussions, improving docs, or sending a PR; no formal status required or conferred) and Maintainers (hold merge rights). Maintainers are named in https://github.com/gma1k/podtrace/blob/main/MAINTAINERS.md and their per-path review authority is encoded in https://github.com/gma1k/podtrace/blob/main/CODEOWNERS, which GitHub enforces as required approvals.

    Decision-making: decisions are made in the open on the pull request or issue that proposes them, with the bar scaled to how hard the change is to reverse. Bug fixes, docs, tests, and dependency bumps need a PR with CODEOWNERS approval. New features, probes, and adapters need a feature request or epic issue first so the shape is agreed before code is written. Changes to the public surface (CRDs, CLI flags, Helm values, env vars) additionally require an explicit read of STABILITY.md, with breaking changes marked in the commit subject and accompanied by a migration note. Security fixes are handled privately under SECURITY.md until an advisory ships.

    Dispute resolution: disagreements are resolved by discussion on the thread. Where consensus is not reached, maintainers decide, and are required to state their reasoning in the thread rather than merging silently.

    Role changes: maintainership follows demonstrated work (a track record of merged non-trivial contributions, reviews that catch real problems, and sustained engagement) and is extended by invitation from existing maintainers. Maintainers who step back are recorded as emeritus rather than removed. Governance changes themselves go through the same PR process as code, proposed as their own PR.

    Related: code of conduct and its enforcement path at https://github.com/gma1k/podtrace/blob/main/CODE_OF_CONDUCT.md, and support and communication channels at https://github.com/gma1k/podtrace/blob/main/SUPPORT.md


    Ya kutosha kwa nishani!

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

    Podtrace has adopted the Contributor Covenant, version 2.1, as its code of conduct, posted at the standard repository-root location:
    https://github.com/gma1k/podtrace/blob/main/CODE_OF_CONDUCT.md

    Because the file is CODE_OF_CONDUCT.md at the root, GitHub detects it automatically and surfaces it in the repository's Community Standards profile and in the contributor-facing prompts on issues and pull requests. The canonical upstream text is linked at https://www.contributor-covenant.org/version/2/1/code_of_conduct/

    Scope: the code of conduct applies to all project-managed spaces (issue tracker, pull requests, discussions, and official off-platform communication) and to individuals officially representing the project in public. It addresses behavior within the project community only.

    Reporting: concerns are reported privately to the maintainer. All reports are reviewed and investigated promptly and fairly, and the maintainer is obligated to respect the privacy and security of the reporter.

    Enforcement: the project applies the Contributor Covenant Enforcement Guidelines (https://www.contributor-covenant.org/version/2/1/code_of_conduct/#enforcement-guidelines), with four escalating levels: correction, warning, temporary ban, and permanent ban. Enforcement authority rests with the maintainer listed in https://github.com/gma1k/podtrace/blob/main/MAINTAINERS.md, consistent with the maintainer-led model documented in https://github.com/gma1k/podtrace/blob/main/GOVERNANCE.md


    Ya kutosha kwa nishani!

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

    Podtrace documents its roles and their responsibilities across two linked files, plus a machine-enforced ownership map.

    Roles are defined in https://github.com/gma1k/podtrace/blob/main/GOVERNANCE.md#roles
    Contributors are anyone who opens an issue, answers a question in Discussions, improves docs, or sends a pull request; no formal status is required and none is conferred. Maintainers hold merge rights.

    Maintainer responsibilities and required tasks are listed in https://github.com/gma1k/podtrace/blob/main/MAINTAINERS.md#what-maintainers-do
    Maintainers: (1) review and merge pull requests and are the required approvers under CODEOWNERS; (2) triage incoming issues, apply area and type labels, and close duplicates; (3) cut releases following the release flow in CONTRIBUTING.md; (4) handle private vulnerability reports under SECURITY.md; (5) decide what lands in the public surface governed by STABILITY.md.

    Several of these tasks carry documented, measurable commitments. SECURITY.md (https://github.com/gma1k/podtrace/blob/main/SECURITY.md) binds vulnerability handling to acknowledgement within 3 business days, triage and confirmation within 7 business days, and a default 90-day coordinated disclosure window. CODE_OF_CONDUCT.md (https://github.com/gma1k/podtrace/blob/main/CODE_OF_CONDUCT.md) assigns code-of-conduct enforcement to the maintainer under the Contributor Covenant Enforcement Guidelines.

    Contributor-side responsibilities are documented in https://github.com/gma1k/podtrace/blob/main/CONTRIBUTING.md, covering DCO sign-off, Conventional Commit format, the required test plan, and regeneration of manifests and clientsets when API types change.

    Who holds which role: MAINTAINERS.md names the current maintainer (Ghassan Malke, GitHub @gma1k) with contact details and areas of ownership. Per-path review authority is encoded in https://github.com/gma1k/podtrace/blob/main/CODEOWNERS, which GitHub enforces as required approval, making the role assignment machine-checkable rather than only asserted in prose. MAINTAINERS.md requires that the maintainer list, CODEOWNERS, and the repository's collaborator settings be updated together, so the documented roster cannot silently diverge from the enforced one.

    Role changes: https://github.com/gma1k/podtrace/blob/main/GOVERNANCE.md#becoming-a-maintainer describes how maintainership is earned (a track record of merged non-trivial contributions, reviews that catch real problems, demonstrated compatibility judgment, and sustained engagement), with invitations extended by existing maintainers. Maintainers who step back are recorded as emeritus rather than removed.


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Podtrace currently has one maintainer, which the project states openly in its roadmap rather than leaving implicit. Continuity is addressed through a documented succession arrangement:
    https://github.com/gma1k/podtrace/blob/main/GOVERNANCE.md#continuity

    Credentials: the maintainer's GitHub account credentials, including two-factor recovery codes, are held by a designated successor through emergency access on the project's credential manager. GitHub account access transitively covers everything required to continue the project: the repository, its issue tracker, branch protection settings, the ghcr.io/gma1k container and chart registry namespaces, and repository secrets. The successor can therefore create and close issues, approve and merge pull requests, and publish a release well within one week of confirmed loss of support.

    Signing keys: podtrace holds no private signing keys, so there is no key material that can be lost with an individual. All artifacts are signed with cosign keyless via GitHub OIDC, with signing events recorded in the public Sigstore Rekor transparency log (see https://github.com/gma1k/podtrace/blob/main/.github/workflows/release.yml). Any successor with repository write access produces signatures that verify identically to those issued today.

    Release process: releases are fully automated via release-please and GitHub Actions using the workflow's built-in GITHUB_TOKEN, and are documented at https://github.com/gma1k/podtrace/blob/main/CONTRIBUTING.md. No personal credentials or undocumented local tooling are required to cut a release. The one external token, used for OperatorHub publication, is [held by the successor / reissuable by the successor following the steps documented in the continuity section].

    Legal rights and domain names: podtrace uses no custom domain. The podtrace.io string appears solely as a Kubernetes annotation namespace and requires no DNS registration, so no domain transfer or testamentary instrument is required. The project is licensed Apache-2.0 (with GPL-2.0 for the eBPF programs under bpf/) and holds no trademark or infrastructure assets requiring transfer.

    Fork rights: as a FLOSS project under Apache-2.0, the full history and build tooling are public, so continuation by fork is available to the community independent of any individual.


    Kwa shida ya kutosha kwa nishani.

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

    Podtrace does not currently meet this criterion. The project has a bus factor of 1.

    Measurement: of 311 human-authored commits (excluding renovate and dependabot), 307 are from the sole maintainer. The remaining four are one-off contributions from four separate individuals, none of whom has sustained involvement. Under the truck-factor methodology of Cosentino et al., removing the single maintainer orphans effectively the entire codebase.

    The project states this openly rather than leaving it implicit. https://github.com/gma1k/podtrace/blob/main/ROADMAP.md names project sustainability as roadmap item 10: "Podtrace has one maintainer. That is the single largest risk to anyone adopting it, more than any individual feature, and it is worth naming plainly rather than leaving implicit. A second maintainer with real review authority is the goal."

    Mitigations in place, aimed at the criterion's concern that a project stalls for lack of knowledgeable personnel:

    Knowledge is externalized rather than tacit. The repository carries 37 reference documents at https://github.com/gma1k/podtrace/tree/main/docs, covering system architecture, eBPF internals, the event schema, the development workflow, kernel and Kubernetes compatibility constraints, and end-to-end verification procedure. The kernel-version and BTF pitfalls that would otherwise exist only as maintainer expertise are documented.

    Intended behavior is captured executably. The tree contains 525 Go test files against 313 non-test source files, plus 22 chainsaw end-to-end scenarios that exercise the operator and agent against a real cluster. A successor can verify correctness without reconstructing intent.

    The release process requires no individual. Releases are automated end to end via release-please and GitHub Actions, with keyless cosign signing through GitHub OIDC, so no private key or undocumented local tooling is involved. The process is documented at https://github.com/gma1k/podtrace/blob/main/CONTRIBUTING.md

    A documented path to a second maintainer exists at https://github.com/gma1k/podtrace/blob/main/GOVERNANCE.md#becoming-a-maintainer, with criteria based on demonstrated contribution and review quality, and per-path review authority tracked in https://github.com/gma1k/podtrace/blob/main/CODEOWNERS

    As an Apache-2.0 project with full public history and reproducible build tooling, continuation by fork is available to the community independent of any individual.

    Raising the bus factor to 2 is an active goal, tracked as roadmap.


  • Nyaraka


    Ya kutosha kwa nishani!

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

    Podtrace maintains a roadmap covering both intended work and explicit non-goals:
    https://github.com/gma1k/podtrace/blob/main/ROADMAP.md

    What the project intends to do: the roadmap lists ten items grouped into Now, Next, and Later horizons. Near-term work covers reconciling the documented CRD inventory, publishing a per-CRD v1beta1 readiness assessment, and completing the supply-chain baseline with SLSA provenance and an OpenSSF Security Insights manifest. Medium-term work covers defining a formal API deprecation policy, graduating individual CRDs from v1alpha1 to v1beta1, resolving whether to ship conversion webhooks, and making the importable Go API usable externally through runnable godoc examples. Longer-term work covers reaching v1.0.0 against the gates defined in https://github.com/gma1k/podtrace/blob/main/STABILITY.md, stating platform support in CI-verified versus best-effort tiers, and recruiting a second maintainer.

    What the project intends not to do: the roadmap includes an explicit Non-goals section. Podtrace will not become a non-Linux agent, because its tracing core is eBPF and therefore Linux-kernel bound by construction. It will not become a policy engine, admission controller, or service mesh, because it observes workloads rather than admitting, mutating, or routing them. It will not implement agent self-update, so that agent version remains whatever the operator deploys and upgrades stay under the cluster owner's control. Non-goals are open to challenge through project Discussions.

    Time horizon: the roadmap deliberately records themes and rough ordering rather than dates or quarters, on the stated reasoning that a roadmap with slipped quarters is worse than no roadmap. The scope covers well beyond one year: v1.0.0 is described as downstream of every other item and "not near," and the intervening work (per-CRD API graduation, a deprecation policy, a conversion story, supply-chain attestation, and tiered platform support) represents multi-year effort at the project's current capacity. Version-gating rules are kept separately in STABILITY.md so the roadmap states direction while STABILITY.md states commitments.

    The roadmap is kept current: its status table reflects the shipped v0.14.x line and the 22 end-to-end chainsaw suites present in the repository. It is linked from the project README and cross-referenced from GOVERNANCE.md and CONTRIBUTING.md.


    Ya kutosha kwa nishani!

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

    Podtrace documents its high-level design across a set of indexed architecture documents, entry point at https://github.com/gma1k/podtrace/blob/main/docs/README.md

    Primary architecture document: https://github.com/gma1k/podtrace/blob/main/docs/architecture.md
    Describes the system's major components and how they relate: eBPF programs running in the kernel (kprobes, uprobes, and tracepoints), a shared ring-buffer map carrying events across the kernel/userspace boundary, and a Go userspace layer comprising the tracer lifecycle manager, the object loader, the probe attachment layer, the event parser, and the cgroup filter that scopes events to a target pod. It documents the end-to-end data flow from kernel event through ring buffer, cgroup filtering, and enrichment, to the output surfaces (live CLI diagnostics, Prometheus metrics, and trace exporters).

    Podtrace runs in three modes, each documented:

    CLI: https://github.com/gma1k/podtrace/blob/main/docs/cli-architecture.md explains the node-spawn model. The CLI does not load eBPF on the invoking workstation; it identifies the node hosting each target pod and runs a short-lived privileged pod on that node, so the kernel loading eBPF is the same kernel running the target workload. The document states the structural reason: eBPF executes in the kernel where it is loaded, so a workstation kernel has no visibility into a remote node's processes or cgroups.

    Operator and agent: https://github.com/gma1k/podtrace/blob/main/docs/operator.md documents the control plane. An operator Deployment runs three reconcilers, each owning one CRD. TracerConfigReconciler manages cluster-wide infrastructure including the agent ServiceAccount, RBAC, and the agent DaemonSet. PodTraceReconciler handles continuous tracing and aggregates per-node status. PodTraceSessionReconciler handles bounded diagnose sessions by spawning per-node Jobs. The agent DaemonSet runs one pod per node and performs the actual kernel-level tracing.

    Per-session Jobs: documented in https://github.com/gma1k/podtrace/blob/main/docs/crd-podtracesession.md, including the per-session Role and RoleBinding the operator generates to scope report writes.

    Kernel-side design detail is in https://github.com/gma1k/podtrace/blob/main/docs/ebpf-internals.md and the binary wire format crossing the kernel/userspace boundary is specified in https://github.com/gma1k/podtrace/blob/main/docs/event-schema.md

    Key architectural properties are documented alongside the structure: the privilege model for each component (unprivileged operator, agent with CAP_BPF and CAP_PERFMON, session Jobs inheriting the agent's capability set) in https://github.com/gma1k/podtrace/blob/main/SECURITY.md; cgroup-based event isolation to the target pod; and cross-namespace consent gating enforced at both reconcile and admission, in https://github.com/gma1k/podtrace/blob/main/docs/cross-namespace-cr-targeting.md

    Supported kernel, Kubernetes, and architecture matrices are in https://github.com/gma1k/podtrace/blob/main/docs/compatibility.md


    Ya kutosha kwa nishani!

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

    Podtrace documents its security requirements, including both the guarantees it provides and the limits it explicitly does not cover, primarily in:
    https://github.com/gma1k/podtrace/blob/main/SECURITY.md

    What users can expect. The security model section states the privilege posture and blast radius of each component. The operator runs unprivileged (distroless nonroot, no host mounts); a compromised operator can only manipulate CRDs in its own namespace and cannot escalate to host privileges directly. The agent DaemonSet runs with CAP_BPF, CAP_PERFMON, and hostPID on each node, and the documentation states plainly that a compromised agent is roughly equivalent to a compromised privileged workload on that node. Per-session Jobs inherit the agent's capability set and are confined to the same single-node blast radius.

    Tenant isolation is the central guarantee, because podtrace observes decrypted application-layer traffic. Cross-namespace tracing is consent-gated: a namespaced custom resource may target pods in a foreign namespace only when that namespace opts in via the podtrace.io/allow-tracing-from annotation. This is enforced by the operator at every reconcile, which is authoritative, and by a validating webhook at admission for fast feedback. Without the grant, a custom resource is confined to its own namespace and cannot capture another tenant's decrypted L7 traffic, DNS queries, syscalls, or file paths. Full semantics are documented at https://github.com/gma1k/podtrace/blob/main/docs/cross-namespace-cr-targeting.md

    Supply-chain guarantees: all published artifacts (container image, Helm chart, release tarballs) are signed with cosign keyless via GitHub OIDC, with signing events recorded in the public Sigstore Rekor transparency log. Verification commands are documented at https://github.com/gma1k/podtrace/blob/main/docs/installation.md

    What users cannot expect. SECURITY.md contains an explicit out-of-scope section. Issues in upstream Kubernetes, the host kernel's BPF verifier, and third-party exporters are not in scope. Attacks that presuppose an adversary already holding cluster-admin privileges are stated to be outside the threat model. Denial of service through excessive trace events on the agent's ring buffer is a user-side concern, with the bounding controls named (samplePercent and thresholds). Development-only paths are excluded.

    Feature-level limits are documented the same way. https://github.com/gma1k/podtrace/blob/main/docs/crypto-detection.md states that AF_ALG crypto-socket detection is observation rather than enforcement: it surfaces use of the vulnerable interface, but does not block the syscall, does not detect exploitation, and is not a substitute for patching. It is also off by default.

    Security-relevant defaults are documented at https://github.com/gma1k/podtrace/blob/main/docs/configuration.md, including that PII redaction (PODTRACE_REDACT_PII) and DNS-name stripping (PODTRACE_REDACT_DNS_NAMES) are disabled by default, and that plaintext export to non-loopback hosts is disabled by default and must be explicitly enabled.

    Hardening guidance for deployments where attacker capability is a concern, covering image digest pinning, RBAC restriction of custom-resource creation, narrow granting of the cross-namespace annotation, and per-node session capacity caps, is in the hardening section of SECURITY.md, with per-distribution notes (SELinux, AppArmor, Pod Security Standards) in the platform guides under https://github.com/gma1k/podtrace/tree/main/docs

    Supported versions and the backport window are stated at the top of SECURITY.md.


    Ya kutosha kwa nishani!

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

    kubectl apply -f https://github.com/gma1k/podtrace/releases/latest/download/quickstart.yaml
    kubectl apply -f https://github.com/gma1k/podtrace/releases/latest/download/quickstart-demo.yaml

    podtrace -n production my-pod # realtime trace
    podtrace -n production my-pod --diagnose 30s --export json # bounded diagnose with a JSON report

    Prerequisites (kernel 5.8 or later, BTF availability, Kubernetes 1.28 or later) are stated in the installation guide and detailed at https://github.com/gma1k/podtrace/blob/main/docs/compatibility.md, with the full CLI reference at https://github.com/gma1k/podtrace/blob/main/docs/usage.md and a documentation index at https://github.com/gma1k/podtrace/blob/main/docs/README.md


    Si ya kutosha kwa nishani.

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

    Podtrace treats documentation currency as part of the change process rather than as periodic cleanup.

    Process: the pull request template at https://github.com/gma1k/podtrace/blob/main/.github/PULL_REQUEST_TEMPLATE.md requires contributors to confirm that user-facing changes are accompanied by updates under docs/, and that generated manifests and clientsets are regenerated and committed when API types change. CODEOWNERS routes documentation changes for review alongside code.

    Evidence of currency: the configuration reference at https://github.com/gma1k/podtrace/blob/main/docs/configuration.md documents every user-facing environment variable the codebase reads. A diff of documented variables against those referenced in source shows no undocumented user-facing options; the only variables absent from the documentation are internal test fixtures. The roadmap at https://github.com/gma1k/podtrace/blob/main/ROADMAP.md reflects the currently shipped release line and the actual count of end-to-end test suites in the repository. The changelog at https://github.com/gma1k/podtrace/blob/main/CHANGELOG.md is generated automatically from Conventional Commits by release-please on every release, so version history cannot drift from what shipped.

    Version differences: https://github.com/gma1k/podtrace/blob/main/STABILITY.md documents what each version line promises, the rules governing when custom resource definitions may change incompatibly, and the graduation gates from v1alpha1 to v1beta1 and from v0.x to v1.0.0. https://github.com/gma1k/podtrace/blob/main/docs/migration.md provides a translation table for users moving between the CLI and custom-resource workflows.

    Defect handling: documentation defects are tracked and fixed like code defects. Recent examples: [link the issues you open] corrected an undercount of the custom resource definition inventory in STABILITY.md, corrected the quickstart command sequence in the README to apply both released manifests in the required order, and updated docs/architecture.md to cover all three deployment modes (CLI node-spawn, operator with agent DaemonSet, and per-session Jobs) and to align its stated capability requirements with SECURITY.md. Known documentation inconsistencies identified during review of the OpenSSF Best Practices criteria have been resolved.

    The documentation set is indexed at https://github.com/gma1k/podtrace/blob/main/docs/README.md and spans 37 reference documents covering architecture, installation, per-CRD field references, eBPF internals, the event wire format, compatibility matrices, and per-platform guides.


    Ya kutosha kwa nishani!

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

    The podtrace repository front page identifies and hyperlinks its achievements in a badge block at the top of the README, above the project description:
    https://github.com/gma1k/podtrace#readme

    The OpenSSF Best Practices badge is displayed and hyperlinked to the project's badge entry at https://www.bestpractices.dev/projects/12882

    The badge is embedded using the dynamic badge image endpoint (https://www.bestpractices.dev/projects/12882/badge) rather than a static image. BadgeApp serves that endpoint with the project's current attainment level, so any change in badge level is reflected on the repository front page immediately and automatically, with no commit required. The 48-hour requirement is therefore satisfied structurally: the displayed badge cannot become stale relative to the recognition it represents.

    Other achievements identified and hyperlinked in the same badge block:

    OpenSSF Scorecard, linked to the project's live Scorecard report at https://scorecard.dev/viewer/?uri=github.com/gma1k/podtrace, also served as a dynamic badge reflecting the current score.
    Artifact Hub, linked to the published Helm repository listing at https://artifacthub.io/packages/helm/podtrace/podtrace
    eBPF Landscape, linked to the ebpf.io applications listing at https://ebpf.io/applications/
    FOSSA license compliance and security status, linked to the project's FOSSA reports.
    RepoGrade, linked to https://www.repo-grade.com/report/gma1k/podtrace
    Go Reference (pkg.go.dev), release version, CI build status, test results, and test coverage.
    Two further external acceptances are identified and hyperlinked in the README body, each of which required passing a third-party review process for inclusion: the OperatorHub.io community operator catalog (https://operatorhub.io/operator/podtrace) and the Kubernetes krew plugin index (https://krew.sigs.k8s.io/), through which podtrace is installable as kubectl krew install podtrace.


  • Ufikiaji na kimataifa


    Ya kutosha kwa nishani!

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

    Podtrace produces a command-line tool and a Kubernetes operator. It has no graphical or web user interface of its own, so the criterion applies chiefly to terminal output and to project documentation.

    Color is never the sole means of conveying information (WCAG 2.0 guideline 1.4.1). Podtrace's CLI emits no color at all: the codebase includes no terminal-color dependency and no ANSI color escape sequences in any output path. All diagnostic information is conveyed through text and document structure, so output remains fully intelligible when piped, redirected to a file, or read by a screen reader. Text contrast (guideline 1.4.3) is governed entirely by the user's own terminal configuration.

    Text alternatives are provided for non-text content (guideline 1.1). Every image on the repository front page, including the project logo and all status badges, carries a descriptive alt attribute: https://github.com/gma1k/podtrace#readme. All documentation is authored in Markdown, which renders as semantic HTML and degrades cleanly to plain text.

    All functionality is available from a keyboard (guideline 2.1). The CLI requires no pointer input, and the operator interface is declarative YAML applied with kubectl, so every capability is keyboard-driven and scriptable.

    Terminal output integrity: podtrace displays data captured from traced application traffic, which is untrusted input. The project strips ANSI escape sequences from captured payloads before display, with test coverage for both color and cursor-movement injection. This prevents captured data from corrupting terminal state or disrupting assistive-technology output.

    Screen-reader considerations: the optional real-time display refreshes by redrawing the report every five seconds, which produces overdraw. The project documents alternative output modes that avoid this entirely and provide identical information: bounded diagnose mode (--diagnose), structured JSON export (--export json), and the PodTraceSession custom resource, which writes its report to a Kubernetes ConfigMap or to object storage. These are documented at https://github.com/gma1k/podtrace/blob/main/docs/usage.md and https://github.com/gma1k/podtrace/blob/main/docs/viewing-events.md, so no capability is available only through the refreshing display.

    The project ships an optional Grafana dashboard definition for its Prometheus metrics. Rendering and accessibility of that dashboard are governed by the user's own Grafana instance, which provides its own accessibility settings, rather than by podtrace.


    Ya kutosha kwa nishani!

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

    Internationalization does not meaningfully apply to podtrace's output.

    Podtrace is a kernel-level tracing tool. Its user-facing output consists overwhelmingly of technical identifiers that are fixed by the systems being observed and are not translatable: kernel symbol names (tcp_v4_connect, vfs_read, do_sys_openat2), syscall names, socket address families (AF_ALG, AF_INET), Linux capability names (CAP_BPF, CAP_PERFMON), protocol identifiers (TCP, UDP, DNS, HTTP/3, QUIC, gRPC), cgroup paths, filesystem paths, and Kubernetes API object kinds and field paths. These appear identically regardless of locale, because they are the names the kernel and the Kubernetes API themselves use.

    The remaining prose is a thin layer of report section headings and summary labels wrapped around that technical content. Localizing it would degrade rather than improve usability: an operator reading a translated heading above untranslated kernel symbols must still search for those symbols in English in kernel documentation, source, and logs, so a partially translated report is harder to act on than a consistent one.

    Locale-dependent formatting defects, which are the substantive risk this criterion guards against, are absent. All timestamps are emitted in locale-independent form: RFC 3339 in structured output and an explicit UTC pattern in report filenames. The codebase performs no locale-dependent number or date formatting. Sorting throughout the diagnostic layer is by event count, timestamp, or machine identifier rather than by locale-sensitive collation of human-readable text, so no incorrect ordering behavior exists in any locale.

    Where podtrace's data is consumed by presentation layers that may serve a localized audience, it is emitted as structured data rather than prose: JSON export, OpenTelemetry traces (OTLP, Jaeger, Splunk, DataDog, Zipkin), and Prometheus metrics. Any downstream dashboard or integration can render that data in its users' language without podtrace being localized. See https://github.com/gma1k/podtrace/blob/main/docs/viewing-events.md and https://github.com/gma1k/podtrace/blob/main/docs/tracing-exporters.md


  • Mengine


    Ya kutosha kwa nishani!

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

    The project stores no passwords for authentication of external users.

    Podtrace operates no website of its own. There is no documentation site, no GitHub Pages deployment, and no custom domain; documentation is Markdown rendered directly in the repository. All project sites are hosted by GitHub: the repository, issue tracker, discussions, and pull requests at https://github.com/gma1k/podtrace, release downloads at https://github.com/gma1k/podtrace/releases, and the container image and Helm OCI chart in GitHub Container Registry at ghcr.io/gma1k.

    All inbound authentication for these surfaces is performed by GitHub, and this criterion states that the use of GitHub meets it. The project itself neither implements nor stores credentials for external user authentication.

    Remaining project-related listings (Artifact Hub, OperatorHub.io, the krew index, pkg.go.dev, OpenSSF Scorecard, FOSSA) are third-party services not operated by the project.


 Udhibiti wa Mabadiliko 0/1 ●

  • Matoleo ya awali


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

 Kuripoti 1/3 ●

  • Mchakato wa kuripoti hitilafu


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Onyo: Inahitaji sababu ndefu zaidi.


  • Mchakato wa kuripoti udhaifu


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Ya kutosha kwa nishani!

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

    https://github.com/gma1k/podtrace/security/advisories/new [vulnerability_report_process] [osps_vm_01_01]


 Ubora 5/19 ●

  • Viwango vya msimbo


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

  • Mfumo wa ujenzi unaofanya kazi


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

  • Mfumo wa usakinishaji


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Ya kutosha kwa nishani!

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

    [osps_do_07_01]


  • Vipengee vilivyotunzwa nje


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    [osps_br_05_01]

    Onyo: URL inahitajika, lakini hakuna URL iliyopatikana.


    Ya kutosha kwa nishani!

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

    Each workflow and job declares a narrowly scoped permissions: block: contents: read for build/test/lint/scan jobs, pull-requests: write only for labeling, security-events: write only for CodeQL upload, and contents: write / packages: write / id-token: write only in release jobs. [osps_vm_05_03]


    Ya kutosha kwa nishani!

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

    [osps_qa_02_01]


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

  • Seti ya majaribio otomatiki


    Ya kutosha kwa nishani!

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

    [test_continuous_integration] [osps_qa_06_01]


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

  • Upimaji wa utendaji mpya


    Ya kutosha kwa nishani!

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

    [tests_documented_added] [osps_qa_06_03]


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Onyo: Inahitaji sababu ndefu zaidi.


  • Bendera za maonyo


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Onyo: Inahitaji sababu ndefu zaidi.


 Usalama 1/13 ●

  • Maarifa ya maendeleo yenye usalama


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Onyo: Inahitaji sababu ndefu zaidi.


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

  • Kutolewa kwa usalama


    Ya kutosha kwa nishani!

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

    [osps_do_03_02]


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

  • Masuala mengine ya usalama


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Every workflow in .github/workflows/ declares an explicit top-level permissions: block scoped to the minimum needed (contents: read for all CI/test/scan workflows), so no job inherits broader permissions than the pipeline grants. [osps_sa_03_01]

    Onyo: URL inahitajika, lakini hakuna URL iliyopatikana.


 Uchanganuzi 0/2 ●

  • Uchambuzi tuli wa msimbo


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Onyo: Inahitaji sababu ndefu zaidi.


  • Uchambuzi wa msimbo wa nguvu za ziada


    Taarifa inayohitajika haijulikani, si ya kutosha kwa nishani.

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

    Onyo: Inahitaji sababu ndefu zaidi.



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 Ghassan Malke na wachangiaji wa nishani ya Mazoea Bora ya OpenSSF.

Ingizo la nishani ya mradi linamilikiwa na: Ghassan Malke.
Ingizo liliundwa siku 2026-05-18 11:01:40 UTC, iliyosasishwa mara ya mwisho siku 2026-08-06 19:53:50 UTC. Ilipata mara ya mwisho nishani ya kupita siku 2026-05-18 11:12:38 UTC.