Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 14:41 UTC

limbo-works / Limbo.Umbraco.Boolean

Boolean property editor for Umbraco.

C#MIT★ 0 stars⑂ 0 forkssince Nov 2021View on GitHub ↗

#limbo #skybrud #umbraco-v8 #umbraco-package #umbraco #umbraco-packages #umbraco-v10 #umbraco-v11 #umbraco-v9

limbo-works/Limbo.Umbraco.Boolean holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on Vitality (55/100) and lowest on Engineering Quality (25/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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.

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)

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

Ownership

LimboOrganization · verified domain

23 followers69 public repossince Dec 2019

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
NuGet	Limbo.Umbraco.Boolean	13.0.0	-	11	938 days ago	umbraco property editor boolean checkbox toggle limbo skybrud umbraco-marketplace

Metrics by category

Vitality

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

55Moderate · 21% of overall

Development activity

36Weak

How it's scored

36/36	Push recency — last push 6 days ago
0/36	Commit cadence — 0/52 weeks with commits
0/18	Commit volume — 0 commits in the last year
0/10	OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Inputs used

commits_last_year	0
human_commit_share	1
days_since_last_push	6
active_weeks_last_year	0

Release discipline

84Excellent

How it's scored

27/27	Ships releases — 13 releases published
36/36	Release recency — latest release 6 days ago
12.6/27	Release cadence — a release every ~173.4 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	13
latest_release_tag	v17.0.0-alpha001
releases_from_tags	no
days_since_latest_release	6
mean_days_between_releases	173.4

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?

32At Risk · 17% of overall

Popularity & adoption

1Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 0 forks
0/15	Watchers — 2 watchers

Inputs used

forks	0
stars	0
watchers	2
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	4
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

57Moderate

How it's scored

45.9/80	Total downloads — 26,118 downloads all-time across nuget
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	Limbo.Umbraco.Boolean
dependents	—
ecosystems	nuget
total_downloads	26,118
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?

41Weak · 23% of overall

Maintainer resilience (bus factor)

20At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0/22.5	Commit distribution — top contributor authored 100% of commits
1.4/13.5	Contributor breadth — 1 contributors
10/10	OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

1Critical

How it's scored

0/42	Issue resolution — no issues or no data
0/30	PR acceptance — no decided pull requests or no data
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	0
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	0
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

85Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
9.9/25	Owner reach — 23 followers of limbo-works
25/25	Track record — 69 public repos, account ~6 yr old

Inputs used

followers	23
owner_type	Organization
is_verified	yes
owner_login	limbo-works
public_repos	69
account_age_days	2,462

Package maintenance

69Good

How it's scored

25/25	Published & resolvable — 1 package(s) on nuget
4/35	Publish recency — latest publish 938 days ago
20/20	Version history — 11 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	Limbo.Umbraco.Boolean
ecosystems	nuget
any_deprecated	no
min_days_since_publish	938

Engineering Quality

Are baseline engineering and documentation practices in place?

25At Risk · 19% of overall

Engineering practices

8Critical

How it's scored

0/24	CI workflows
0/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — no data

Inputs used

has_ci	no
has_tests	no
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
10/10	Topics — 9 topics
0/10	Wiki

Inputs used

topics	limbo, skybrud, umbraco-v8, umbraco-package, umbraco, umbraco-packages, umbraco-v10, umbraco-v11, umbraco-v9
has_wiki	no
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

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

5.2/7.5	Binary-Artifacts — binaries present in source code
0/7.5	Branch-Protection — no data
0/2.5	CI-Tests — no data
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 5 contributing companies or organizations
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
0/7.5	Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — no SAST tool detected
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	11
scorecard_version	v5.5.0
checks_inconclusive	7
scorecard_aggregate	3

Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, 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.

31At Risk · 4% of overall

Agent context & guidance

2Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
2.4/40	Legible commit history — 2 of 44 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.045
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

26At Risk

How it's scored

12.6/18	One-command bootstrap — src/Limbo.Umbraco.Boolean/Limbo.Umbraco.Boolean.csproj (toolchain convention, no task runner)
0/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — C# (statically typed)
0/10	Reproducible environment
0/10	Demonstrated agent practice — no agent-authored commits among the last 44
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	no
lockfiles	—
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	src/Limbo.Umbraco.Boolean/Limbo.Umbraco.Boolean.csproj
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — C# (statically typed)
55/55	Manageable file sizes — 0/6 source files over 60KB

Inputs used

primary_language	C#
largest_source_bytes	1,901
source_files_sampled	6
oversized_source_files	0

Key facts

0GitHub stars

1contributors

0commits, last 12 months

6days since last push

13releases

1bus factor

0open issues

—package ecosystems

Data collection warnings

No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 3.0 / 10

3.0aggregate

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-15 14:40 UTC

7	Binary-Artifacts	binaries present in source code
n/a	Branch-Protection	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
n/a	CI-Tests	no pull request found
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/30 approved changesets -- score normalized to 0
10	Contributors	project has 5 contributing companies or organizations
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	no SAST tool detected
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
10	Vulnerabilities	0 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
NuGet	Umbraco.Cms.Core	`[13.0.0,13.999)`	src/Limbo.Umbraco.Boolean/Limbo.Umbraco.Boolean.csproj
NuGet	Umbraco.Cms.Web.Website	`[13.0.0,13.999)`	src/Limbo.Umbraco.Boolean/Limbo.Umbraco.Boolean.csproj
NuGet	Umbraco.Cms.Web.BackOffice	`[13.0.0,13.999)`	src/Limbo.Umbraco.Boolean/Limbo.Umbraco.Boolean.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.

Registry	Package	Version	Relation
NuGet	Umbraco.Cms.Core	`—`	direct
NuGet	Umbraco.Cms.Web.BackOffice	`—`	direct
NuGet	Umbraco.Cms.Web.Website	`—`	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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records