Not a repository list.
A continuously evolving engineering workbench.
Real platform problems become OSS systems, integration seams are verified, and progress stays visible through commits, releases, documentation and operating records.
See the whole portfolio before exploring each project.
Explore project status, dependencies, adoption and maintenance coverage in the OpenForge portfolio dashboard. Select any project to inspect its details and connected repositories.
Explore portfolio dashboardBased on published portfolio data, not live operational telemetry
Understand the practice
Why OSS explains the engineering practice behind the repositories.
Explore the systems
Browse standards, platform, capabilities, data and AI/edge projects.
Follow the evolution
Engineering Story shows how the judgement evolved over time.
Measure momentum without inventing a maturity score.
Activity, releases, contributors and repository age come from the build-time GitHub snapshot. Documentation coverage comes from the site content index. These are operating signals, not popularity or quality scores.
repositories pushed within seven days of the metadata snapshot
projects with at least one GitHub release
repositories reporting more than one contributor
projects whose repository age is at least 180 days
91 project documentation sections are indexed
Turn observable gaps into the next maintenance queue.
These are factual maintenance signals derived from repository and documentation snapshots, not severity scores. Existing trackers show live issue state; untracked signals may show a keyword-matched open issue only as a Candidate, never as an automatic tracker assignment.
Group untracked signals before creating new backlog.
The owner below is only the nearest canonical portfolio source, not an automatically assigned issue. Candidate matching is equally conservative: it is a review hint based on title/label keywords, not proof that the issue owns the gap.
Canonical checklist for release, SBOM, provenance and release-evidence gaps.
Repository snapshot reports zero releases.
Compare public-OSS readiness without inventing a composite score.
Governance and security come from the repository tree audit, release and community from the GitHub snapshot, docs from the site index, and adoption only from an explicit evidence registry. Tracker state and candidate issue matches are review aids and never override current repository evidence.
| Project | Governance | Release | Docs | Security | Community | Adoption evidence |
|---|---|---|---|---|---|---|
| Narwhal → audit not indexed | Not indexed | Observed | 9 docs | Not indexed | 2+ contributors | Not indexed |
| Narwhal Portal → audit not indexed | Not indexed | Observed | 5 docs | Not indexed | 2+ contributors | Not indexed |
| NFS Quota Agent → audit not indexed | Not indexed | Observed | 7 docs | Not indexed | 2+ contributors | Not indexed |
| ldapium → audit not indexed | Not indexed | Observed | 5 docs | Not indexed | 2+ contributors | Not indexed |
| Kube-Ready-Box → audit not indexed | Not indexed | Observed | 5 docs | Not indexed | 2+ contributors | Not indexed |
| ClusterDeck → audit not indexed | Not indexed | Observed | 3 docs | Not indexed | 2+ contributors | Not indexed |
| Beluga → audit not indexed | Not indexed | Observed | 9 docs | Not indexed | 2+ contributors | Not indexed |
| KubeMetal → audit not indexed | Not indexed | Observed | 5 docs | Not indexed | 2+ contributors | Not indexed |
| OpenForge → audit not indexed | Not indexed | No GitHub release | 40 docs | Not indexed | 2+ contributors | Not indexed |
projects with at least one reported or verified external-use record
explicit sources reviewed as external use or downstream integration
explicit reports awaiting stronger verification
gap-local open issues suggested by deterministic title/label matching
Accepted adoption evidence kinds are external adopter, external contributor with downstream use, user report, public deployment, and downstream integration. Every record requires a source URL. Stars, forks, clone counts, and aggregate contributor totals are intentionally excluded.
Turn missing evidence into a reviewable action queue.
Each item is generated from explicit audit or snapshot absence. Canonical tracker links remain authoritative; a matching open issue from the same repository is shown only as a Candidate for review.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No root/.github SECURITY evidence was observed.
No SBOM/SPDX/CycloneDX evidence path was observed in the repository tree.
Audit matching, issue-candidate matching, and adoption discovery are intentionally conservative. Candidate signals never become trackers or adoption evidence automatically.
One data model for development state and cross-project impact.
Each OSS proposes verified state through an OpenForge PR. The merged registry is the official source of truth rendered here.
Only projects with OpenForge-verified, PR-merged state are shown here.
Review possible external-use signals before they become evidence.
Build-time GitHub code search can add exact repository-URL mentions as candidates, but intake remains separated from readiness evidence. Automated candidates never change adoption readiness until a source is reviewed and promoted.
source discovered, review pending
explicit report, stronger validation pending
reviewed external-use evidence
reviewed but not acceptable as adoption evidence
Promotion rule: candidate → reported only when a source explicitly describes actual use; reported → verified only after the source and project relationship are reviewed. A manual review record overrides the same automated source URL, so rejected decisions persist across future discovery runs.
Build-time GitHub snapshot across the OSS portfolio.
Read the work from standards to workloads.
This is not a runtime dependency graph. It shows recurring engineering practice and real usage paths across independent OSS projects.
See role, maturity, verification and live repository pulse at a glance.
Static role and verification boundaries stay documentation-driven, while commits, releases, contributors and repository freshness come from the build-time GitHub metadata snapshot.
| Project | Role / Stage | Verification | Repository pulse | Freshness | Independence |
|---|---|---|---|---|---|
| Narwhal → dasomel/narwhal | Flagship Platform Active platform | Regression + live checks | 1,209 commits · 5 releases 3 contributors · latest v1.3.0 | active · 1d 2026-10-22 | Platform root |
| Narwhal Portal → dasomel/narwhal-portal | Platform Experience Layer Active UI layer | Build + in-cluster workflow | 416 commits · 6 releases 2 contributors · latest v1.0.17 | active · 7d 2026-10-15 | Narwhal-coupled |
| NFS Quota Agent → dasomel/nfs-quota-agent | Reusable Component Reusable component | Filesystem + operational checks | 646 commits · 16 releases 3 contributors · latest v0.5.0 | recent · 11d 2026-10-12 | Independent |
| ldapium → dasomel/ldapium | Identity Infrastructure Prototype | Helm test + supply-chain evidence | 510 commits · 5 releases 2 contributors · latest v0.3.0 | active · 1d 2026-10-21 | Independent |
| Kube-Ready-Box → dasomel/kube-ready-box | Node Foundation Reusable foundation | OS readiness validation | 291 commits · 6 releases 2 contributors · latest v1.1.0 | recent · 19d 2026-10-04 | Independent |
| ClusterDeck → dasomel/clusterdeck | Workstation Access Layer MVP / early | SSH + kubeconfig + API | 304 commits · 5 releases 2 contributors · latest v0.4.1 | active · 0d 2026-10-22 | Independent |
| Beluga → dasomel/beluga | Data Platform Reference Reference platform | 2 E2E data paths | 802 commits · 1 releases 2 contributors · latest v0.1.0 | active · 0d 2026-10-22 | Reference environment |
| KubeMetal → dasomel/kubemetal | Emerging / Cloud-native AI Emerging | Measured local baseline | 453 commits · 2 releases 2 contributors · latest v0.2.0 | active · 0d 2026-10-22 | Independent lab system |
| OpenForge → dasomel/openforge | Engineering Foundation Standards system | Standards → reference loop | 279 commits · 0 releases 3 contributors · latest — | active · 0d 2026-10-22 | Cross-project |
OSS 프로젝트를 반복 가능하게 만들고, 로컬 Kubernetes 노드·접속 경로·공급망 기준을 표준화하는 기반 프로젝트
OpenForge
An OSS engineering foundation combining a blueprint, Engineering Operating Model, executable governance, agent security, and a portfolio control plane
As an OSS portfolio grows, repository documentation, CI, security, agent instructions, releases, and maintenance state evolve independently, making implementation claims and evidence drift apart
Kube-Ready-Box
Kubernetes-ready Ubuntu 24.04/26.04 LTS Vagrant Base Boxes for ARM64/AMD64, ext4/XFS, and local hypervisors
Local Kubernetes projects repeatedly rebuild the same OS, kernel, networking, storage, and diagnostic baseline across architectures and hypervisors
ClusterDeck
A macOS desktop tool that discovers frequently recreated VM/Kubernetes environments and automates SSH and kubeconfig access around stable Profiles
Frequently recreated VM and Kubernetes labs change IP addresses, forcing users to rebuild SSH aliases, bastion/ProxyJump paths, remote kubeconfigs, and local contexts by hand
Kubernetes 기반 플랫폼, 관리 포털, 스토리지 enforcement, directory infrastructure를 구성하는 프로젝트
Narwhal
A reproducible and verifiable Kubernetes Internal Developer Platform
Integrating dozens of cloud-native components creates recurring DNS, TLS, identity, networking, startup-order, and version-compatibility failures that must be re-proven after upgrades
Narwhal Portal
Operations and developer workbench for the Narwhal Kubernetes Internal Developer Platform
A Kubernetes IDP can expose dozens of independent dashboards while leaving platform-wide state, relationships, and operator workflows fragmented
NFS Quota Agent
Kubernetes agent that enforces filesystem Project Quotas for NFS PersistentVolumes
Kubernetes NFS PersistentVolumes can expose requested capacity without enforcing an equivalent filesystem-level limit on the shared NFS storage
ldapium
An OpenLDAP Kubernetes packaging stack built from upstream source: server, management UI, Helm, and offline delivery
OpenLDAP deployment options often combine stale images, inconsistent packaging, default-credential risks, and incomplete ARM64/offline support
CDC부터 lakehouse, query, orchestration까지 데이터 lifecycle을 통합하고 운영하는 프로젝트
Apple Silicon 기반 local MLOps와 simulation-to-edge Physical AI infrastructure를 검증하는 프로젝트
KubeMetal
An Apple Silicon hybrid MLOps desktop app separating Kubernetes control from native macOS MLX compute
Apple Silicon Metal compute cannot simply be treated as ordinary Linux VM compute, so an all-in-Kubernetes MLOps architecture leaves local hardware underused
Siqoq
A Physical AI infrastructure experiment that preserves semantic event and action contracts from simulation to edge hardware
Perception-to-action workflows become difficult to reuse and verify when simulators, laptops, sensors, and actuators expose unrelated APIs and runtime assumptions
Code evolves with documentation.
The work does not end at README.
Problem · Architecture · Decision · Verification · Operations · Troubleshooting · ADR keep implementation and engineering judgement together.