Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-25 14:16 UTC

Excel-DNA / IntelliSense

Add in-sheet IntelliSense for Excel UDFs

C#MIT★ 179 stars⑂ 55 forkssince Jul 2013View on GitHub ↗

Excel-DNA/IntelliSense holds a health index of 35 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (60/100) and lowest on Engineering Quality (21/100). It was last updated 80 days ago. A single contributor accounts for most of its recent work.

35
overall / 100
Weak

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.

35
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 40 is calibrated to 35 on the published index scale (record calibration 2026-08-02).

Ownership

Excel-DNAOrganization
176 followers23 public repossince Jan 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetExcelDna.IntelliSense1.9.0-20372 days agoexcelexceldnaudfexcel-dnaintellisense

Metrics by category

Vitality

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

31At Risk · 21% of overall
How it's scored
18/36Push recency — last push 80 days ago
0.7/36Commit cadence — 1/52 weeks with commits
2.7/18Commit volume — 1 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share1
days_since_last_push80
active_weeks_last_year1
How it's scored
27/27Ships releases — 39 releases published
7.2/36Release recency — latest release 459 days ago
12.6/27Release cadence — a release every ~202.7 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count39
latest_release_tagv1.9.0
releases_from_tagsno
days_since_latest_release459
mean_days_between_releases202.7

Community & Adoption

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

59Moderate · 17% of overall
How it's scored
36.5/60Stars — 179 stars
14.4/25Forks — 55 forks
7.9/15Watchers — 27 watchers
Inputs used
forks55
stars179
watchers27
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
58.4/80Total downloads — 419,039 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesExcelDna.IntelliSense
dependents—
ecosystemsnuget
total_downloads419,039
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.9/22.5Commit distribution — top contributor authored 74% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.736
How it's scored
25.1/42Issue resolution — 60% of issues closed
26.5/30PR acceptance — 23/26 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 4/20 approved changesets -- score normalized to 2
Inputs used
merged_prs23
open_issues47
closed_issues70
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.598
closed_unmerged_prs3
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.2/25Owner reach — 176 followers of Excel-DNA
22.1/25Track record — 23 public repos, account ~14 yr old
Inputs used
followers176
owner_typeOrganization
is_verifiedno
owner_loginExcel-DNA
public_repos23
account_age_days5,357
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
14/35Publish recency — latest publish 372 days ago
20/20Version history — 20 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesExcelDna.IntelliSense
ecosystemsnuget
any_deprecatedno
min_days_since_publish372

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

27At Risk · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 4/20 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 16 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.5/40Legible commit history — 31 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.31
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Source/ExcelDna.IntelliSense.Host/ExcelDna.IntelliSense.Host.csproj, Source/ExcelDna.IntelliSense.Tools/ExcelDna.IntelliSense.Tools.csproj, Source/ExcelDna.IntelliSense/ExcelDna.IntelliSense.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsSource/ExcelDna.IntelliSense.Host/ExcelDna.IntelliSense.Host.csproj, Source/ExcelDna.IntelliSense.Tools/ExcelDna.IntelliSense.Tools.csproj, Source/ExcelDna.IntelliSense/ExcelDna.IntelliSense.csproj
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/32 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes30,632
source_files_sampled32
oversized_source_files0

Key facts

179GitHub stars
10contributors
1commits, last 12 months
80days since last push
39releases
1bus factor
47open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 55 ⇿
0Stars
55Forks
39Releases

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.

01020304050605422015-102020-112025-12
Major 1Minor 5Patch 11

Each point covers 10 days.

OpenSSF Scorecard 2.7 / 10
2.7aggregate

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-25 14:16 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 4/20 approved changesets -- score normalized to 2
10Contributorsproject has 16 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
NuGetExcelDna.AddIn—Source/ExcelDna.IntelliSense.Host/ExcelDna.IntelliSense.Host.csproj
NuGetExcelDna.AddIn—Source/ExcelDna.IntelliSense.Tools/ExcelDna.IntelliSense.Tools.csproj
NuGetExcelDna.Interop—Source/ExcelDna.IntelliSense/ExcelDna.IntelliSense.csproj
NuGetExcelDna.Integration—Source/ExcelDna.IntelliSense/ExcelDna.IntelliSense.csproj
All dependencies 3

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

RegistryPackageVersionRelation
NuGetExcelDna.Addin—direct
NuGetExcelDna.Integration—direct
NuGetExcelDna.Interop—direct
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.