The NetBSD Foundation
The US nonprofit foundation handles project assets, support and institutional continuity for NetBSD. This profile assesses the enabling institution without treating every source file as covered by a single inspected license.
90% of weighted axes reviewed. A mechanism hypothesis, not proven effectiveness or a donation recommendation.
Who this work enables
Tools & support for charities: Shared project assets, administrative continuity and technical knowledge can help public-interest developers reuse a portable operating-system ecosystem.
Humanity’s Checklist source match
Gatekeepers · Coordination — editorial, partial alignment.
A reusable software institution can reduce dependence on proprietary gatekeepers and coordinate contributions. This partial mapping does not establish social impact, security or beneficiary decision rights.
Explicit checklist adoption: not verified. A mechanism match is not an affiliation, endorsement, evidence of effectiveness or a scoring bonus. Read the practice.
Focus classification: 2026-10-27. Based on the organization’s dated official sources below; earlier axis-review dates are unchanged.
Compare alternatives for a funder →
The proposed pathway
Provide durable legal and contributor infrastructure for a portable operating-system commons
Six dimensions, with rationale
Structural depth
3 / 4Shared assets and support for a portable software commons can reduce infrastructure dependency, without alone changing the institutions using it.
Institutional reach
4 / 4A portable base system can support diverse public-interest and other applications across platforms rather than one local program.
Durability
3 / 4Institutional assets and reusable source can persist across grants, but maintenance, hardware adaptation and contributor continuity still need resources.
Scalability
3 / 4A common base can be adapted across deployments; specialized hardware work and system administration limit low-cost replication.
Funding additionality
UnreviewedNo current marginal foundation funding gap or displacement of other project contributions was established.
Community agency
UnreviewedThe foundation page documents developer-elected directors, but developer membership is not equivalent to binding rights for affected downstream communities.
Evidence and selection
Organization reported; current primary mechanism sources inspected
Illustrative inclusion to examine this mechanism. Inclusion is not an external recommendation or a verified comparative ranking.
A testable next question
Do nonprofit implementers supported by NetBSD’s shared institutional infrastructure sustain useful portable systems with better exit options and lower lifecycle burden than comparable teams relying on existing alternatives?
Review confidence: Moderate for documented design; low for systemic attribution. The NetBSD Foundation’s nonprofit asset, legal and contributor-support role, not sole authorship of the operating system or a blanket license certification of its source tree.
What remains uncertain
The foundation identifies itself as a Delaware-incorporated 501(c)(3). Its licensing page distinguishes several BSD forms and per-file terms. The inspected GitHub source conversion warns that commit links can change; a root license endpoint did not supply a scoped current packet, so no license-checked badge is awarded here. That is not evidence of closed code. No security, portability, governance or lifecycle-cost audit occurred, and contributor voting does not establish downstream community agency.
Sources to inspect
- NetBSD Foundation: current nonprofit identity, assets and governance ↗
official · checked 2026-10-27 - NetBSD: project, contributors and foundation relationship ↗
official · checked 2026-10-27 - NetBSD: licensing and redistribution distinctions ↗
official · checked 2026-10-27 - NetBSD source conversion: inspected repository and link-stability warning ↗
official · checked 2026-10-27
Propose a sourced correction →
Axis review: 2026-10-27 · weighting method v0.2 (2026-10-26) · Method, conflicts and coverage