Repo brief: nissl-lab/npoi

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:00:35.783Z · commit 46544cc845b4

Verdict

Healthy — Strong maintenance signals

• Last commit 2w ago
• 7 active contributors
• Apache-2.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

NPOI is a .NET library that reads and writes Microsoft Office file formats (Excel 2003/2007 .xls/.xlsx, Word .docx) without requiring Microsoft Office or COM interop installed. It's a direct port of Apache POI to C#, enabling pure managed code manipulation of office documents across Windows and Linux. Monorepo structure: OpenXmlFormats/ contains 60+ auto-generated C# classes mirroring Office Open XML schema (Bibliography.cs, Chart/.cs, Drawing/.cs); core NPOI.SS namespace (Spreadsheet) and NPOI.XWPF (Word) provide high-level APIs; Directory.Build.props and Directory.Packages.props centralize .NET build configuration; GitHub Actions workflows (CI.yml, opencode.yml) orchestrate testing and…

Start here

Open these first:

• OpenXmlFormats/OOXMLFactory.cs — Core factory for creating OpenXML format objects; entry point for document parsing and serialization across all Office…
• OpenXmlFormats/Spreadsheet/Document/WorkbookDocument.cs — Root document class for Excel workbooks; demonstrates the pattern for all Office document types in the codebase.
• OpenXmlFormats/Spreadsheet/Document/WorksheetDocument.cs — Worksheet model for Excel sheets; illustrates how content documents are structured and linked to parent documents.
• OpenXmlFormats/Drawing/Chart/ChartSpaceDocument.cs — Chart document model; shows how embedded drawing objects are represented in OpenXML format.
• Directory.Build.props — Global build configuration and package versioning; defines NuGet dependencies and compilation settings for all projects.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/nissl-lab/npoi.git
cd npoi
# NUKE build system (see .nuke/build.schema.json)
./build.ps1  # Windows
./build.sh   # Linux/macOS
dotnet build npoi.sln
dotnet test  # Run test suite

Daily commands:

# Full build & test
./build.ps1 -Target Test  # Windows NUKE
./build.sh --target Test   # Linux NUKE

# Or direct dotnet
dotnet build npoi.sln
dotnet test npoi.sln --configuration Release

# Create NuGet package
dotnet pack npoi.sln --configuration Release --output ./artifacts

Key cautions & unknowns

• Concentrated ownership — top contributor handles 55% of recent commits
• EULA/Licensing: Binary releases require OSMF maintenance fee payment since v2.8.0 (see OSMFEULA.txt)—open source projects and non-revenue users exempt but must verify status. Auto-generated code:…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.