Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 21:35 UTC

dotnet / interactive-window

Visual Studio Interactive Window

C# · PowerShell · ShellMIT★ 74 stars⑂ 41 forkssince Jun 2016View on GitHub ↗

dotnet/interactive-window holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (68/100) and lowest on AI Readiness (25/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

.NET PlatformOrganization
22,989 followers278 public repossince Oct 2014

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

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
36/36Push recencylast push 7 days ago
18/36Commit cadence26/52 weeks with commits
14.3/18Commit volume38 commits in the last year
7/10OpenSSF Scorecard: Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year38
human_commit_share
days_since_last_push7
active_weeks_last_year26
How it's scored
27/27Ships releases2 releases published
0/36Release recencylatest release 2,958 days ago
12.6/27Release cadencea release every ~299.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagVisual-Studio-2017-Update-7
releases_from_tagsno
days_since_latest_release2,958
mean_days_between_releases299.2
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?

57Moderate · 17% of overall
How it's scored
30.2/60Stars74 stars
13.4/25Forks41 forks
6.7/15Watchers17 watchers
Inputs used
forks41
stars74
watchers17
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.4/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth20 contributors
10/10OpenSSF Scorecard: Contributorsproject has 13 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.536
How it's scored
14.5/42Issue resolution35% of issues closed
26.9/30PR acceptance237/264 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs237
open_issues17
closed_issues9
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.346
closed_unmerged_prs27
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach22,989 followers of dotnet
25/25Track record278 public repos, account ~11 yr old
Inputs used
followers22,989
owner_typeOrganization
is_verified
owner_logindotnet
public_repos278
account_age_days4,299
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsvisualstudio, interactivewindow, interactive, scripting, editor
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?

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 13 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
5.2/7.5Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, 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.

25At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
54.1/55Manageable file sizes2/118 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes148,929
source_files_sampled118
oversized_source_files2

Key facts

74GitHub stars
20contributors
38commits, last 12 months
7days since last push
2releases
1bus factor
17open issues
package ecosystems

More detail

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-07-18 21:35 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 13 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 30

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

RegistryPackageVersionRelation
NuGetBasicUndoindirect
NuGetDrop.Appindirect
NuGetMicrosoft.DotNet.IBCMergeindirect
NuGetMicrosoft.Guardian.Cli0.109.0indirect
NuGetMicrosoft.ManifestTool.CrossPlatformindirect
NuGetMicrosoft.VisualStudio.ComponentModelHostindirect
NuGetMicrosoft.VisualStudio.CoreUtilityindirect
NuGetMicrosoft.VisualStudio.Editorindirect
NuGetMicrosoft.VisualStudio.ImageCatalogindirect
NuGetMicrosoft.VisualStudio.Imagingindirect
NuGetMicrosoft.VisualStudio.Interopindirect
NuGetMicrosoft.VisualStudio.Language.Intellisenseindirect
NuGetMicrosoft.VisualStudio.Language.StandardClassificationindirect
NuGetMicrosoft.VisualStudio.Platform.VSEditorindirect
NuGetMicrosoft.VisualStudio.SDK.Analyzersindirect
NuGetMicrosoft.VisualStudio.Shell.15.0indirect
NuGetMicrosoft.VisualStudio.Shell.Frameworkindirect
NuGetMicrosoft.VisualStudio.Telemetryindirect
NuGetMicrosoft.VisualStudio.Text.Dataindirect
NuGetMicrosoft.VisualStudio.Text.Logicindirect
NuGetMicrosoft.VisualStudio.Text.UIindirect
NuGetMicrosoft.VisualStudio.Text.UI.Wpfindirect
NuGetMicrosoft.VisualStudio.Threadingindirect
NuGetMicrosoft.VisualStudio.Utilitiesindirect
NuGetMicrosoft.VisualStudio.Validationindirect
NuGetMicrosoft.VisualStudioEng.MicroBuild.Coreindirect
NuGetMicrosoft.VisualStudioEng.MicroBuild.Plugins.SwixBuildindirect
NuGetMoqindirect
NuGetNewtonsoft.Jsonindirect
NuGetSystem.Collections.Immutableindirect
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.14.0 — full methodology · metrics wiki.

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