aminya/setup-cpp holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (75/100) and lowest on Security (58/100). It was last updated today. A single contributor accounts for most of its recent work.
78
overall / 100
Good
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.
78
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).
Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25
Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40
No advisories left outstanding — no advisory carries a publication date
Inputs used
source
osv
advisories
0
affected_packages
0
assessed_packages
17
unassessed_packages
80
affected_by_severity
none
direct_affected_packages
0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 17 resolved dependencies against OSV. 80 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.
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.
API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20
MCP server — not applicable to this kind of software
40/40
Runnable examples — examples
Inputs used
example_dirs
examples
has_mcp_signal
no
api_schema_files
—
interfaces_expected_of
—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.
Key facts
277GitHub stars
7contributors
114commits, last 12 months
0days since last push
100releases
1bus factor
18open issues
npmpackage ecosystems
Data collection warnings
Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
Star and fork history 0 ★ / 37 ⇿
0Stars
37Forks
97Releases
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.
Major 1Minor 48Patch 46
Each point covers 5 days.
OpenSSF Scorecard 4.8 / 10
4.8aggregate
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 12:39 UTC
internal error: vulnerabilitiesClient.ListUnfixedVulnerabilities: osvscanner.DoScan: client error: status="400 Bad Request" body={"code":3,"message":"error in query at index 16: rpc error: code = InvalidArgument desc = invalid hash"}
All dependencies 97
Full resolved dependency set from the GitHub dependency graph: 0 direct and 97 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
Registry
Package
Version
Relation
npm
@actions/cache
^4.0.2
indirect
npm
@actions/core
^1.11.1
indirect
npm
@actions/core
^2.0.0
indirect
npm
@actions/exec
^1.1.1
indirect
npm
@actions/http-client
2.2.3
indirect
npm
@actions/io
^1.1.3
indirect
npm
@actions/tool-cache
^2.0.2
indirect
npm
@aminya/minijson
1.1.3
indirect
npm
@babel/core
^7.26.9
indirect
npm
@babel/preset-typescript
^7.27.1
indirect
npm
@biomejs/biome
^1.9.4
indirect
npm
@iarna/toml
^2.2.5
indirect
npm
@liuli-util/vite-plugin-node
^0.10.0
indirect
npm
@octokit/core
^7.0.0
indirect
npm
@octokit/openapi-types
^25.0.0
indirect
npm
@octokit/plugin-paginate-rest
^13.0.0
indirect
npm
@octokit/plugin-rest-endpoint-methods
^16.0.0
indirect
npm
@octokit/rest
^22.0.0
indirect
npm
@octokit/types
^14.0.0
indirect
npm
@pnpm/patching.apply-patch
^1000.0.7
indirect
npm
@shockpkg/archive-files
3.2.5
indirect
npm
@swc/jest
^0.2.37
indirect
npm
@types/babel__core
~7.20.5
indirect
npm
@types/cross-spawn
^6.0.6
indirect
npm
@types/cross-spawn
~6.0.6
indirect
npm
@types/escape-quotes
~1.0.0
indirect
npm
@types/eslint
^9.6.1
indirect
npm
@types/fs-extra
^11.0.4
indirect
npm
@types/iarna__toml
~2.0.5
indirect
npm
@types/jest
^29.5.14
indirect
npm
@types/memoizee
0.4.12
indirect
npm
@types/memoizee
^0.4.11
indirect
npm
@types/node
25.9.8
indirect
npm
@types/node
^22.13.8
indirect
npm
@types/node
^25.0.0
indirect
npm
@types/semver
^7.5.8
indirect
npm
@types/which
^3.0.0
indirect
npm
@types/which
^3.0.4
indirect
npm
@types/which
~3.0.4
indirect
npm
admina
1.0.1
indirect
npm
admina
^1.0.1
indirect
npm
caxa
^3.0.1
indirect
npm
ci-info
^4.0.0
indirect
npm
ci-info
^4.1.0
indirect
npm
cross-env
7.0.3
indirect
npm
cross-spawn
7.0.6
indirect
npm
cross-spawn
^7.0.6
indirect
npm
cspell
^9.0.0
indirect
npm
diagnostics_channel
^1.1.0
indirect
npm
dprint
^0.57.0
indirect
npm
escape-path-with-spaces
^1.0.2
indirect
npm
escape-quotes
^1.0.2
indirect
npm
escape-string-regexp
^5.0.0
indirect
npm
eslint
^8.57.1
indirect
npm
eslint-config-atomic
^1.22.1
indirect
npm
execa
7.2.0
indirect
npm
execa
^7.2.0
indirect
npm
fast-glob
^3.3.3
indirect
npm
fs-extra
^11.3.0
indirect
npm
is-url-online
^1.5.0
indirect
npm
jest
^29.7.0
indirect
npm
lefthook
^2.0.14
indirect
npm
macos-release
^3.3.0
indirect
npm
memoizee
^0.4.17
indirect
npm
minimatch
^10.2.6
indirect
npm
mkdirp
^3.0.1
indirect
npm
mri
^1.2.0
indirect
npm
node-downloader-helper
2.1.11
indirect
npm
npm-check-updates
^19.3.1
indirect
npm
npm-run-all2
^8.0.4
indirect
npm
numerous
1.0.3
indirect
npm
p-timeout
^6.1.4
indirect
npm
path-exists
5.0.0
indirect
npm
path-exists
^5.0.0
indirect
npm
patha
0.4.1
indirect
npm
patha
^0.4.1
indirect
npm
randomuuid-polyfill
^1.0.2
indirect
npm
readme-md-generator
^1.0.0
indirect
npm
retry-as-promised
^7.1.1
indirect
npm
rollup
^4.34.9
indirect
npm
safe-stable-stringify
^2.5.0
indirect
npm
semver
7.8.5
indirect
npm
shx
0.4.0
indirect
npm
simple-update-notifier
^2.0.0
indirect
npm
timers-browserify
^2.0.12
indirect
npm
ts-node
^10.9.2
indirect
npm
ts-readme
^1.1.3
indirect
npm
tsx
^4.20.3
indirect
npm
turbo
2.11.3
indirect
npm
typescript
^5.8.2
indirect
npm
ubuntu-version
^2.0.0
indirect
npm
util.types
^0.0.2
indirect
npm
vite
^7.3.1
indirect
npm
vite-plugin-babel
^1.3.0
indirect
npm
web-streams-polyfill
^4.1.0
indirect
npm
which
4.0.0
indirect
npm
which
^4.0.0
indirect
Dependency advisories 0
This repository publishes no package the index resolves, so its own dependency graph was assessed — 17 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 80 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.
No known advisories affect the assessed dependencies.
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.
Related records
Inspected repositories sharing catalogue tags or ecosystems with aminya/setup-cpp. Read them side by side →
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.
