Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 14:38 UTC

VION-IoT / vion-contracts

Shared contract used by several dotnet VION apps like API, Mesh, Dale, Service Providers

C#Apache-2.0★ 1 star⑂ 0 forkssince Apr 2026View on GitHub ↗

VION-IoT/vion-contracts holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (83/100) and lowest on Security (30/100). It was last updated today. 2 contributors account for most of its recent work.

60
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.

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

Ownership

VION IoTOrganization
0 followers6 public repossince Oct 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetVion.Contracts11.0.2-520 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall

Development activity

71Good
How it's scored
36/36Push recency — last push 0 days ago
11.1/36Commit cadence — 16/52 weeks with commits
17.2/18Commit volume — 81 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year81
human_commit_share1
days_since_last_push0
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 54 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~4.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count54
latest_release_tagv11.0.2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases4.8

Community & Adoption

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

42Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

77Good
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Ecosystem adoption (downloads)

58Moderate
How it's scored
46/80Total downloads — 26,627 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesVion.Contracts
dependents—
ecosystemsnuget
total_downloads26,627
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?

68Good · 23% of overall

Maintainer resilience (bus factor)

45Weak
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.4/22.5Commit distribution — top contributor authored 49% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled3
top_contributor_share0.494

Issue & PR responsiveness

100Exceptional
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 26/26 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs26
open_issues0
closed_issues0
prs_merged_7d4
prs_decided_7d4
prs_merged_30d7
prs_decided_30d7
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

38Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of VION-IoT
7.9/25Track record — 6 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginVION-IoT
public_repos6
account_age_days326

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 — 52 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesVion.Contracts
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall

Engineering practices

38Weak
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

65Good
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

30At Risk · 16% of overall

Security posture

30At Risk
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsVion.Contracts.AotProof/Vion.Contracts.AotProof.csproj, Vion.Contracts.Test/Vion.Contracts.Test.csproj, Vion.Contracts/Vion.Contracts.csproj
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno

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.

60Moderate · 4% of overall

Agent context & guidance

71Good
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
26/40Legible commit history — 40 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.488
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes10,210

Verify loop (build / test / typecheck)

37Weak
How it's scored
12.6/18One-command bootstrap — Vion.Contracts.AotProof/Vion.Contracts.AotProof.csproj, Vion.Contracts.Test/Vion.Contracts.Test.csproj, Vion.Contracts/Vion.Contracts.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 — 33 of the last 82 commits agent-authored or agent-credited
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.402
toolchain_manifestsVion.Contracts.AotProof/Vion.Contracts.AotProof.csproj, Vion.Contracts.Test/Vion.Contracts.Test.csproj, Vion.Contracts/Vion.Contracts.csproj
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/128 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes39,588
source_files_sampled128
oversized_source_files0

Key facts

1GitHub stars
3contributors
81commits, last 12 months
0days since last push
54releases
2bus factor
0open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/VION-IoT/vion-contracts: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-15T14:38:16Z. Please include `AA00:3EB66B:29056A:27C478:6AA95856` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 9
RegistryPackageVersion constraintManifest
NuGetcoverlet.collector6.0.4Vion.Contracts.Test/Vion.Contracts.Test.csproj
NuGetMicrosoft.NET.Test.Sdk18.0.1Vion.Contracts.Test/Vion.Contracts.Test.csproj
NuGetMSTest4.0.2Vion.Contracts.Test/Vion.Contracts.Test.csproj
NuGetGoogle.FlatBuffers25.2.10Vion.Contracts/Vion.Contracts.csproj
NuGetIsExternalInit1.0.3Vion.Contracts/Vion.Contracts.csproj
NuGetMicrosoft.Extensions.Hosting.Abstractions10.0.0Vion.Contracts/Vion.Contracts.csproj
NuGetRequiredMemberAttribute1.0.0Vion.Contracts/Vion.Contracts.csproj
NuGetSystem.Collections.Immutable10.0.7Vion.Contracts/Vion.Contracts.csproj
NuGetSystem.Text.Json10.0.7Vion.Contracts/Vion.Contracts.csproj
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with VION-IoT/vion-contracts. Read them side by side →

100open-telemetry/opentelemetry-dotnetThe OpenTelemetry .NET ClientExceptional100AvaloniaUI/AvaloniaDevelop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The future of .NET UIExceptional99microsoft/onnxruntime-genaiGenerative AI extensions for onnxruntimeExceptional99App-vNext/PollyPolly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.Exceptional98microsoft/fluentui-blazorMicrosoft Fluent UI Blazor components library. For use with ASP.NET Core Blazor applicationsExceptional98PowerShell/PowerShellPowerShell for every system!Exceptional

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.