Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 14:28 UTC

TrilliumIT / vxrouter

A vxlan networking and ipam plugin for docker clusters.

GoMIT★ 5 stars⑂ 2 forkssince Feb 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

TrilliumIT/vxrouter holds a health index of 14 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (53/100) and lowest on Vitality (19/100). It was last updated 1647 days ago. A single contributor accounts for most of its recent work.

14
overall / 100
Critical

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.

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

Ownership

Trillium StaffingOrganization
0 followers20 public repossince May 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/TrilliumIT/vxrouterv0.0.11-112401 days ago

Metrics by category

Vitality

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

19Critical · 21% of overall
How it's scored
0/36Push recencylast push 1,647 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push1,647
active_weeks_last_year0
How it's scored
27/27Ships releases10 releases published
0/36Release recencylatest release 2,398 days ago
19.8/27Release cadencea release every ~81.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count10
latest_release_tagv0.0.11
releases_from_tagsno
days_since_latest_release2,398
mean_days_between_releases81.3

Community & Adoption

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

29At Risk · 17% of overall
How it's scored
9.8/60Stars5 stars
0/25Forks2 forks
0/15Watchers1 watchers
Inputs used
forks2
stars5
watchers1
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
0/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_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.1/22.5Commit distributiontop contributor authored 60% of commits
2.7/13.5Contributor breadth2 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.597
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance1/1 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
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.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
0/25Owner reach0 followers of TrilliumIT
21.6/25Track record20 public repos, account ~10 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginTrilliumIT
public_repos20
account_age_days3,762
How it's scored
25/25Published & resolvable1 package(s) on go
4/35Publish recencylatest publish 2,401 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/TrilliumIT/vxrouter
ecosystemsgo
any_deprecatedno
min_days_since_publish2,401

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-Tests0 out of 1 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?

22At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities50 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate1.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.
How it's scored
10.2/35Direct dependencies free of known advisories3 affected: github.com/docker/docker 1.13.1 (high 7.5), github.com/sirupsen/logrus 1.4.2 (high 7.5), golang.org/x/net 0.0.0-20200219183655-46282727080f (high 7.5)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
25.6/40No advisories left outstanding3 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,674 days ago
Inputs used
sourceosv
advisories76
affected_packages4
assessed_packages14
unassessed_packages0
affected_by_severityhigh 4
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 14 resolved dependencies against OSV. 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.

36Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.6/40Legible commit history3 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.03
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapgo.mod (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
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 codeGo (statically typed)
55/55Manageable file sizes0/14 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes10,237
source_files_sampled14
oversized_source_files0

Key facts

5GitHub stars
2contributors
0commits, last 12 months
1,647days since last push
10releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 1.6 / 10
1.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-19 14:28 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 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
0Vulnerabilities50 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
Gogithub.com/TrilliumIT/iputilv0.0.0-20180924135734-17ef68da6dffgo.mod
Gogithub.com/coreos/go-systemdv0.0.0-20191104093116-d3cd4ed1dbcfgo.mod
Gogithub.com/docker/dockerv1.13.1go.mod
Gogithub.com/docker/go-plugins-helpersv0.0.0-20200102110956-c9a8a2d92cccgo.mod
Gogithub.com/sirupsen/logrusv1.4.2go.mod
Gogithub.com/urfave/cliv1.22.2go.mod
Gogithub.com/vishvananda/netlinkv1.1.0go.mod
Gogolang.org/x/netv0.0.0-20200219183655-46282727080fgo.mod
All dependencies 14

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

RegistryPackageVersionRelation
Gogithub.com/coreos/go-systemd0.0.0-20191104093116-d3cd4ed1dbcfdirect
Gogithub.com/docker/docker1.13.1direct
Gogithub.com/docker/go-plugins-helpers0.0.0-20200102110956-c9a8a2d92cccdirect
Gogithub.com/sirupsen/logrus1.4.2direct
Gogithub.com/trilliumit/iputil0.0.0-20180924135734-17ef68da6dffdirect
Gogithub.com/urfave/cli1.22.2direct
Gogithub.com/vishvananda/netlink1.1.0direct
Gogolang.org/x/net0.0.0-20200219183655-46282727080fdirect
Gogithub.com/docker/distribution2.7.1+incompatibleindirect
Gogithub.com/docker/go-connections0.4.0indirect
Gogithub.com/docker/go-units0.4.0indirect
Gogithub.com/microsoft/go-winio0.4.14indirect
Gogithub.com/opencontainers/go-digest1.0.0-rc1indirect
Gogithub.com/pkg/errors0.9.1indirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 14 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 3 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
github.com/docker/docker1.13.1directhigh3728.0.0
github.com/sirupsen/logrus1.4.2directhigh21.9.3
golang.org/x/net0.0.0-20200219183655-46282727080fdirecthigh3412.0.2
github.com/docker/distribution2.7.1+incompatibleindirecthigh32.8.0+incompatible

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