Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-22 07:15 UTC

nissl-lab / npoi

a .NET library that can read/write Office formats without Microsoft Office installed. No COM+, no interop.

C#Apache-2.0★ 6,197 stars⑂ 1,491 forkssince Jan 2013View on GitHub ↗

nissl-lab/npoi holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Vitality (88/100) and lowest on Security (42/100). It was last updated today. 2 contributors account for most of its recent work.

34
overall / 100
At Risk

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

34
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 70 is calibrated to 83 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Nissl LabOrganization
74 followers10 public repossince Oct 2020

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetNPOI2.8.1-270 days agoxlsxxlsexcelworddocxofficeole

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
25.6/36Commit cadence — 37/52 weeks with commits
18/18Commit volume — 586 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year586
human_commit_share0.8
days_since_last_push0
active_weeks_last_year37
How it's scored
27/27Ships releases — 23 releases published
36/36Release recency — latest release 0 days ago
12.6/27Release cadence — a release every ~123.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tag2.8.1-rc2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases123.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

82Excellent · 17% of overall
How it's scored
60/60Stars — 6,197 stars
25/25Forks — 1,491 forks
13.6/15Watchers — 278 watchers
Inputs used
forks1,491
stars6,197
watchers278
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Total downloads — 120,246,865 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesNPOI
dependents—
ecosystemsnuget
total_downloads120,246,865
monthly_downloads—
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.4/22.5Commit distribution — top contributor authored 45% of commits
13.5/13.5Contributor breadth — 97 contributors
10/10OpenSSF Scorecard: Contributors — project has 22 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled97
top_contributor_share0.447
How it's scored
40.1/42Issue resolution — 95% of issues closed
25.6/30PR acceptance — 596/698 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/23 approved changesets -- score normalized to 1
Inputs used
merged_prs596
open_issues47
closed_issues967
prs_merged_7d1
prs_decided_7d1
prs_merged_30d9
prs_decided_30d9
issue_closed_ratio0.954
closed_unmerged_prs102
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
13.5/25Owner reach — 74 followers of nissl-lab
19.4/25Track record — 10 public repos, account ~5 yr old
Inputs used
followers74
owner_typeOrganization
is_verifiedno
owner_loginnissl-lab
public_repos10
account_age_days2,162

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
35/35Publish recency — latest publish 0 days ago
20/20Version history — 27 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesNPOI
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://nissl-lab.github.io/npoi/
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsexcel, biff, openxml, word, poi, dotnetcore, office-file-api
has_wikiyes
homepagehttp://nissl-lab.github.io/npoi/
docs_sitehttp://nissl-lab.github.io/npoi/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

42Weak · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/23 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 22 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier28
security_posture_before_jurisdiction56
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
unassessed_packages19
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 5 resolved dependencies against OSV. 19 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

63Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
29.3/40Legible commit history — 44 of 80 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.55
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,804
How it's scored
12.6/18One-command bootstrap — OpenXmlFormats/NPOI.OpenXmlFormats.Core.csproj, benchmarks/NPOI.Benchmarks/NPOI.Benchmarks.csproj, build/_build.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 9 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.09
toolchain_manifestsOpenXmlFormats/NPOI.OpenXmlFormats.Core.csproj, benchmarks/NPOI.Benchmarks/NPOI.Benchmarks.csproj, build/_build.csproj, main/NPOI.Core.csproj, ooxml/NPOI.OOXML.Core.csproj, openxml4Net/NPOI.OpenXml4Net.Core.csproj, scratchpad/HSLF/HSLF.csproj, scratchpad/HSSF/HSSF.csproj, scratchpad/HWPF/HWPF.csproj, solution/NPOI.Pack.csproj, testcases/main/NPOI.TestCases.Core.csproj, testcases/ooxml/NPOI.OOXML.TestCases.Core.csproj, testcases/openxml4net/NPOI.OOXML4Net.TestCases.Core.csproj, testcases/scratchpad/TestCases.csproj, tools/DocPartViewer/DocPartViewer/DocPartViewer.csproj, tools/NPOI.StyleViewer/NPOI.StyleViewer/NPOI.StyleViewer.csproj, tools/XmlSerializationCodeGenerator/XmlSerializationCodeGenerator.csproj
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — C# (statically typed)
54.1/55Manageable file sizes — 50/3,121 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes364,278
source_files_sampled3,121
oversized_source_files50

Key facts

6,197GitHub stars
97contributors
586commits, last 12 months
0days since last push
23releases
2bus factor
47open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 1,491 ⇿
0Stars
1,491Forks
21Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

05001,0001,5001,491142018-042022-062026-09
Major 0Minor 3Patch 7

Each point covers 8 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-22 07:14 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/23 approved changesets -- score normalized to 1
10Contributorsproject has 22 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 32
RegistryPackageVersion constraintManifest
NuGetMicrosoft.SourceLink.GitHub—OpenXmlFormats/NPOI.OpenXmlFormats.Core.csproj
NuGetZString—OpenXmlFormats/NPOI.OpenXmlFormats.Core.csproj
NuGetNuke.Common10.0.0build/_build.csproj
NuGetNuGet.Packaging6.13.1build/_build.csproj
NuGetSystem.Security.Cryptography.Xml10.0.10build/_build.csproj
NuGetEnums.NET—main/NPOI.Core.csproj
NuGetExtendedNumerics.BigDecimal—main/NPOI.Core.csproj
NuGetMathNet.Numerics.Signed—main/NPOI.Core.csproj
NuGetMicrosoft.IO.RecyclableMemoryStream—main/NPOI.Core.csproj
NuGetMicrosoft.SourceLink.GitHub—main/NPOI.Core.csproj
NuGetBouncyCastle.Cryptography—main/NPOI.Core.csproj
NuGetSharpZipLib—main/NPOI.Core.csproj
NuGetSkiaSharp—main/NPOI.Core.csproj
NuGetSkiaSharp.NativeAssets.Linux.NoDependencies—main/NPOI.Core.csproj
NuGetZString—main/NPOI.Core.csproj
NuGetSystem.Text.Encoding.CodePages—main/NPOI.Core.csproj
NuGetMicrosoft.SourceLink.GitHub—ooxml/NPOI.OOXML.Core.csproj
NuGetSkiaSharp—ooxml/NPOI.OOXML.Core.csproj
NuGetSystem.Security.Cryptography.Xml—ooxml/NPOI.OOXML.Core.csproj
NuGetMicrosoft.SourceLink.GitHub—openxml4Net/NPOI.OpenXml4Net.Core.csproj
NuGetBouncyCastle.Cryptography—solution/NPOI.Pack.csproj
NuGetEnums.NET—solution/NPOI.Pack.csproj
NuGetExtendedNumerics.BigDecimal—solution/NPOI.Pack.csproj
NuGetMathNet.Numerics.Signed—solution/NPOI.Pack.csproj
NuGetMicrosoft.IO.RecyclableMemoryStream—solution/NPOI.Pack.csproj
NuGetMicrosoft.SourceLink.GitHub—solution/NPOI.Pack.csproj
NuGetSharpZipLib—solution/NPOI.Pack.csproj
NuGetSkiaSharp—solution/NPOI.Pack.csproj
NuGetSkiaSharp.NativeAssets.Linux.NoDependencies—solution/NPOI.Pack.csproj
NuGetSystem.Security.Cryptography.Xml—solution/NPOI.Pack.csproj
NuGetSystem.Text.Encoding.CodePages—solution/NPOI.Pack.csproj
NuGetZString—solution/NPOI.Pack.csproj
All dependencies 24

Full resolved dependency set from the GitHub dependency graph: 16 direct and 8 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
NuGetBouncyCastle.Cryptography—direct
NuGetEnums.NET—direct
NuGetExtendedNumerics.BigDecimal—direct
NuGetMathNet.Numerics.Signed—direct
NuGetMicrosoft.IO.RecyclableMemoryStream—direct
NuGetMicrosoft.SourceLink.GitHub—direct
NuGetNuGet.Packaging6.13.1direct
NuGetNuke.Common10.0.0direct
NuGetSharpZipLib—direct
NuGetSharpZipLib1.3.3direct
NuGetSkiaSharp—direct
NuGetSkiaSharp.NativeAssets.Linux.NoDependencies—direct
NuGetSystem.Security.Cryptography.Xml—direct
NuGetSystem.Security.Cryptography.Xml10.0.10direct
NuGetSystem.Text.Encoding.CodePages—direct
NuGetZString—direct
NuGetBenchmarkDotNet—indirect
NuGetGitHubActionsTestLogger—indirect
NuGetICSharpCode.TextEditor3.2.1.6466indirect
NuGetMicrosoft.NET.Test.Sdk—indirect
NuGetNSubstitute—indirect
NuGetNUnit—indirect
NuGetNUnit3TestAdapter—indirect
NuGetSystem.Configuration.ConfigurationManager—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 5 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 19 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — NuGet.