Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 05:54 UTC

decentraland / governance

🏢 Governance platform of the Decentraland DAO

TypeScriptCustom license★ 49 stars⑂ 41 forkssince Aug 2020View on GitHub ↗
KindLibraryChat bothow this is determined

decentraland/governance holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (83/100) and lowest on Security (63/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

87
overall / 100
Excellent

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.

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

Ownership

DecentralandOrganization · verified domain
770 followers529 public repossince May 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmgovernance0.0.03512714 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
11.8/36Commit cadence — 17/52 weeks with commits
14.6/18Commit volume — 41 commits in the last year
10/10OpenSSF Scorecard: Maintained — 21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year41
human_commit_share0.99
days_since_last_push2
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~30.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv1.95.9
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases30.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?

64Moderate · 17% of overall
How it's scored
27.3/60Stars — 49 stars
13.4/25Forks — 41 forks
4.7/15Watchers — 8 watchers
Inputs used
forks41
stars49
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.4/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 33 contributors
10/10OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled33
top_contributor_share0.315
How it's scored
37.6/42Issue resolution — 90% of issues closed
28.5/30PR acceptance — 1,273/1,339 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 29/30 approved changesets -- score normalized to 9
Inputs used
merged_prs1,273
open_issues65
closed_issues558
prs_merged_7d5
prs_decided_7d5
prs_merged_30d5
prs_decided_30d7
issue_closed_ratio0.896
closed_unmerged_prs66
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
20.8/25Owner reach — 770 followers of decentraland
25/25Track record — 529 public repos, account ~11 yr old
Inputs used
followers770
owner_typeOrganization
is_verifiedyes
owner_logindecentraland
public_repos529
account_age_days4,158
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 2,714 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgovernance
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,714

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://governance.decentraland.org
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsdao, decentraland, hacktoberfest, blockchain, dapp, ethereum, web3
has_wikino
homepagehttps://governance.decentraland.org
docs_sitehttps://governance.decentraland.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 29/30 approved changesets -- score normalized to 9
2.5/2.5Contributors — project has 7 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 236 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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.

73Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.snapshot.org/llms.txt)
40/40Legible commit history — 98 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.snapshot.org/llms.txt
legible_history_share0.99
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 8 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.08
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.9/55Manageable file sizes — 1/367 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes70,211
source_files_sampled367
oversized_source_files1

Key facts

49GitHub stars
33contributors
41commits, last 12 months
2days since last push
100releases
2bus factor
65open issues
npmpackage 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

More detail

Star and fork history 0 ★ / 41 ⇿
0Stars
41Forks
93Releases

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.

0102030404022021-032023-102026-06
Major 0Minor 3Patch 54

Each point covers 5 days.

OpenSSF Scorecard 6.3 / 10
6.3aggregate

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-10-19 05:54 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 29/30 approved changesets -- score normalized to 9
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities236 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
npm@dcl/feature-flags^1.2.0package.json
npm@dcl/schemas^26.0.0package.json
npm@dcl/ui-env^2.0.0package.json
npm@otterspace-xyz/contracts^2.7.3package.json
npm@pushprotocol/restapi^1.7.3package.json
npm@snapshot-labs/snapshot.js0.10.1package.json
npmchalk^4.1.2package.json
npmdayjs^1.11.9package.json
npmdayjs-precise-range^1.0.1package.json
npmdcl-catalyst-client^22.0.0package.json
npmdecentraland-dapps^28.0.0package.json
npmdecentraland-gatsby^9.0.1package.json
npmdiscord.js^14.7.1package.json
npmdotenv^16.0.0package.json
npmethers^5.7.1package.json
npmlodash^4.17.21package.json
npmnft.storage^7.1.1package.json
npmnode-cache^5.1.2package.json
npmnode-pg-migrate^6.2.1package.json
npmnumeral^2.0.6package.json
npmpg^8.7.3package.json
npmpg-tsquery^8.3.0package.json
npmremark-parse^9.0.0package.json
npmremark-stringify^9.0.1package.json
npmrollbar^2.26.1package.json
npmslug^4.0.4package.json
npmswagger-ui-express^4.6.0package.json
npmunified9.2.2package.json
npmyaml^2.2.1package.json
npmzod^3.22.4package.json
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.

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 — npm.