Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 01:18 UTC

cocos / cocos-ccbuild

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

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

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

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

Ownership

COCOSOrganization
1,306 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.222,36111517 days agococosenginebuildcompile

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 17 days ago
2.1/36Commit cadence — 3/52 weeks with commits
7/18Commit volume — 5 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year5
human_commit_share1
days_since_last_push17
active_weeks_last_year3
How it's scored
27/27Ships releases — 46 releases published
36/36Release recency — latest release 17 days ago
19.8/27Release cadence — a release every ~61.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count46
latest_release_tag2.3.22
releases_from_tagsno
days_since_latest_release17
mean_days_between_releases61.9
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?

30At Risk · 17% of overall
How it's scored
11.3/60Stars — 6 stars
7/25Forks — 8 forks
0/15Watchers — 1 watchers
Inputs used
forks8
stars6
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
45/80Monthly downloads — 2,361 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@cocos/ccbuild
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,361
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.4/22.5Commit distribution — top contributor authored 72% of commits
6.8/13.5Contributor breadth — 5 contributors
0/10OpenSSF Scorecard: Contributors — project 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 resolution — 0% of issues closed
29.4/30PR acceptance — 99/101 decided PRs merged
13/13Newcomer PR acceptance — 3/3 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs99
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
22.4/25Owner reach — 1,306 followers of cocos
25/25Track record — 74 public repos, account ~12 yr old
Inputs used
followers1,306
owner_typeOrganization
is_verifiedno
owner_logincocos
public_repos74
account_age_days4,562

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 17 days ago
20/20Version history — 115 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@cocos/ccbuild
ecosystemsnpm
any_deprecatedno
min_days_since_publish17

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 5 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?

26At Risk · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.2/2.5CI-Tests — 5 out of 30 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/30 approved changesets -- score normalized to 1
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packaging — no data
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 37 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
12/35Direct dependencies free of known advisories — 1 affected: @babel/plugin-transform-modules-systemjs 7.22.11 (high 8.2)
5/25Indirect dependencies free of known advisories — 3 affected: @babel/traverse 7.20.1 (critical 9.3), serialize-javascript 6.0.2 (high 8.1), @babel/core 7.19.6 (low 3.2)
24.4/40No advisories left outstanding — 3 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,058 days ago
Inputs used
sourceosv
advisories5
affected_packages4
assessed_packages380
unassessed_packages0
affected_by_severitycritical 1, high 2, low 1
direct_affected_packages1
Matched the npm:@cocos/ccbuild@2.3.22 runtime dependency closure — what installing the published package pulls in — 380 packages. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 75 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.75
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 — modules/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 environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.2/55Manageable file sizes — 3/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
17days since last push
46releases
1bus factor
1open 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 ★ / 8 ⇿
0Stars
8Forks
45Releases

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.

2345678822023-112025-032026-08
Major 0Minor 3Patch 40

Each point covers 3 days.

OpenSSF Scorecard 2.2 / 10
2.2aggregate

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-09 01:18 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
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
0Vulnerabilities37 existing vulnerabilities detected
Direct dependencies 12
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
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

Dependency advisories 4

Installing npm:@cocos/ccbuild@2.3.22 pulls in 380 packages, direct and transitive: 4 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@babel/traverse7.20.1indirectcritical18.0.0-alpha.4
@babel/plugin-transform-modules-systemjs7.22.11directhigh18.0.0-alpha.13
serialize-javascript6.0.2indirecthigh27.0.5
@babel/core7.19.6indirectlow18.0.0-rc.6

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