Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 02:51 UTC

cocos / cocos-ccbuild

TypeScriptNo license detected★ 6 stars⑂ 7 forkssince Feb 2023View on GitHub ↗

cocos/cocos-ccbuild holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Vitality (65/100) and lowest on Security (23/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

COCOSOrganization
1,279 followers74 public repossince Mar 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@cocos/ccbuild2.3.213,9571141 day agococosenginebuildcompile

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
2.1/36Commit cadence3/52 weeks with commits
7/18Commit volume5 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year5
human_commit_share
days_since_last_push1
active_weeks_last_year3
How it's scored
27/27Ships releases45 releases published
36/36Release recencylatest release 1 days ago
19.8/27Release cadencea release every ~57.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count45
latest_release_tag2.3.21
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases57.7
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?

31At Risk · 17% of overall
How it's scored
11.3/60Stars6 stars
6.5/25Forks7 forks
0/15Watchers1 watchers
Inputs used
forks7
stars6
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
48/80Monthly downloads3,957 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@cocos/ccbuild
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,957
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.4/22.5Commit distributiontop contributor authored 72% of commits
6.8/13.5Contributor breadth5 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.716
How it's scored
0/42Issue resolution0% of issues closed
29.4/30PR acceptance96/98 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs96
open_issues1
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0
closed_unmerged_prs2
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
22.3/25Owner reach1,279 followers of cocos
25/25Track record74 public repos, account ~12 yr old
Inputs used
followers1,279
owner_typeOrganization
is_verified
owner_logincocos
public_repos74
account_age_days4,507
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 1 days ago
20/20Version history114 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@cocos/ccbuild
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests5 out of 30 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

23At Risk · 16% of overall
How it's scored
6/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.2/2.5CI-Tests5 out of 30 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 5/30 approved changesets -- score normalized to 1
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
3/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
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-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities28 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.3
Excluded from scoring (no data or not applicable): 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.

52Moderate · 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
22/22Automated tests
11/11Lint / format config.eslintrc.json
11/11Static type checkingmodules/build-engine/tsconfig.json, modules/bundler/tsconfig.json, modules/dts-bundler/tsconfig.json, modules/modularize/tsconfig.json, modules/stats-query/tsconfig.json, modules/transformer/tsconfig.json, modules/utils/tsconfig.json, test/test-engine-source-pal-precompiled/tsconfig.json, test/test-engine-source-without-symlink/tsconfig.json, test/test-engine-source/tsconfig.json, test/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
6/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsmodules/build-engine/tsconfig.json, modules/bundler/tsconfig.json, modules/dts-bundler/tsconfig.json, modules/modularize/tsconfig.json, modules/stats-query/tsconfig.json, modules/transformer/tsconfig.json, modules/utils/tsconfig.json, test/test-engine-source-pal-precompiled/tsconfig.json, test/test-engine-source-without-symlink/tsconfig.json, test/test-engine-source/tsconfig.json, test/tsconfig.json, tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.2/55Manageable file sizes3/200 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes1,658,433
source_files_sampled200
oversized_source_files3

Key facts

6GitHub stars
5contributors
5commits, last 12 months
1days since last push
45releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Could not fetch npm package '@ccbuild/test' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.3 / 10
2.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-07-16 02:50 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
1CI-Tests5 out of 30 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities28 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
npm@ccbuild/build-engine*package.json
npm@ccbuild/bundler*package.json
npm@ccbuild/dts-bundler*package.json
npm@ccbuild/modularize*package.json
npm@ccbuild/stats-query*package.json
npm@ccbuild/transformer*package.json
npm@ccbuild/utils*package.json
npmdedent^0.7.0package.json
npmfs-extra~11.1.1package.json
npmglob~7.2.0package.json
npmjson5^2.2.3package.json
npmresolve^1.22.1package.json
npm@ccbuild/stats-query*test/package.json
npm@ccbuild/build-engine*test/package.json
npm@ccbuild/dts-bundler*test/package.json
npm@ccbuild/modularize*test/package.json
npm@ccbuild/utils*test/package.json
npmfs-extra~11.1.1test/package.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.11.0 — full methodology · metrics wiki.

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