Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-20 10:04 UTC

contao-components / choices

Choices.js integration

JavaScriptNo license detected★ 0 stars⑂ 2 forkssince Mar 2022View on GitHub ↗

contao-components/choices holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Vitality (66/100) and lowest on AI Readiness (14/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Contao componentsOrganization
2 followers30 public repossince Aug 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistcontao-components/choices11.2.536,431201 day ago

Metrics by category

Vitality

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

66Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
7.6/36Commit cadence — 11/52 weeks with commits
11.1/18Commit volume — 16 commits in the last year
2/10OpenSSF Scorecard: Maintained — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year16
human_commit_share1
days_since_last_push1
active_weeks_last_year11
How it's scored
16.2/27Ships releases — 11 version tags (no GitHub releases)
36/36Release recency — latest release 1 days ago
19.8/27Release cadence — a release every ~50.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tag11.2.5
releases_from_tagsyes
days_since_latest_release1
mean_days_between_releases50.8
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?

26At Risk · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 2 forks
1.7/15Watchers — 3 watchers
Inputs used
forks2
stars0
watchers3
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
60.8/80Monthly downloads — 36,431 downloads/month across packagist
3.2/20Registry dependents — 2 packages depend on it
Inputs used
packagescontao-components/choices
dependents2
ecosystemspackagist
total_downloads336,955
monthly_downloads36,431
unverified_packages_excluded—

Sustainability & Governance

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

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.9/22.5Commit distribution — top contributor authored 69% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.692
How it's scored
42/42Issue resolution — 100% of issues closed
27.7/30PR acceptance — 12/13 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 9/30 approved changesets -- score normalized to 3
Inputs used
merged_prs12
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of contao-components
22.9/25Track record — 30 public repos, account ~12 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_logincontao-components
public_repos30
account_age_days4,474

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 1 days ago
20/20Version history — 20 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescontao-components/choices
ecosystemspackagist
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

17Critical · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 9/30 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
1.5/7.5Maintained — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages159
unassessed_packages1
affected_by_severityhigh 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 159 resolved dependencies against OSV. 1 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.

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.

14Critical · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.4/40Legible commit history — 12 of 39 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.308
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 39
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
18.3/55Manageable file sizes — 2/3 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes209,104
source_files_sampled3
oversized_source_files2

Key facts

0GitHub stars
4contributors
16commits, last 12 months
1days since last push
11releases
1bus factor
0open issues
npm, Packagistpackage ecosystems

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
6Releases

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.

111222212024-122025-072026-02
Major 0Minor 2Patch 4

Each point covers 2 days.

OpenSSF Scorecard 3.2 / 10
3.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-11-20 10:04 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
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 9/30 approved changesets -- score normalized to 3
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
2Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistcontao-components/installer^1.0.9composer.json
All dependencies 160

Full resolved dependency set from the GitHub dependency graph: 1 direct and 159 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Packagistcontao-components/installer—direct
npm@gulpjs/messages1.1.0indirect
npm@gulpjs/to-absolute-glob4.0.0indirect
npmansi-colors1.1.0indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmansi-wrap0.1.0indirect
npmanymatch3.1.3indirect
npmarr-diff4.0.0indirect
npmarr-union3.1.0indirect
npmarray-each1.0.1indirect
npmarray-slice1.1.0indirect
npmassign-symbols1.0.0indirect
npmasync-done2.0.0indirect
npmasync-settle2.0.0indirect
npmb4a1.6.7indirect
npmbach2.0.1indirect
npmbare-events2.6.1indirect
npmbase64-js1.5.1indirect
npmbinary-extensions2.3.0indirect
npmbl5.1.0indirect
npmbraces3.0.3indirect
npmbuffer6.0.3indirect
npmchalk4.1.2indirect
npmchokidar3.6.0indirect
npmcliui7.0.4indirect
npmclone2.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconvert-source-map2.0.0indirect
npmcopy-props4.0.0indirect
npmcss-tree1.1.3indirect
npmcsso4.2.0indirect
npmdetect-file1.0.0indirect
npmeach-props3.0.0indirect
npmemoji-regex8.0.0indirect
npmend-of-stream1.4.5indirect
npmescalade3.2.0indirect
npmexpand-tilde2.0.2indirect
npmextend3.0.2indirect
npmextend-shallow3.0.2indirect
npmfast-fifo1.3.2indirect
npmfast-levenshtein3.0.0indirect
npmfastest-levenshtein1.0.16indirect
npmfastq1.19.1indirect
npmfill-range7.1.1indirect
npmfindup-sync5.0.0indirect
npmfined2.0.0indirect
npmflagged-respawn2.0.0indirect
npmfor-in1.0.2indirect
npmfor-own1.0.0indirect
npmfs-mkdirp-stream2.0.1indirect
npmfsevents2.3.3indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmglob-parent5.1.2indirect
npmglob-parent6.0.2indirect
npmglob-stream8.0.3indirect
npmglob-watcher6.0.0indirect
npmglobal-modules1.0.0indirect
npmglobal-prefix1.0.2indirect
npmglogg2.2.0indirect
npmgraceful-fs4.2.11indirect
npmgulp5.0.1indirect
npmgulp-cli3.1.0indirect
npmgulp-csso4.0.1indirect
npmgulp-rename2.1.0indirect
npmgulplog2.2.0indirect
npmhas-flag4.0.0indirect
npmhasown2.0.2indirect
npmhomedir-polyfill1.0.3indirect
npmiconv-lite0.6.3indirect
npmieee7541.2.1indirect
npminherits2.0.4indirect
npmini1.3.8indirect
npminterpret3.1.1indirect
npmis-absolute1.0.0indirect
npmis-binary-path2.1.0indirect
npmis-core-module2.16.1indirect
npmis-extendable1.0.1indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-negated-glob1.0.0indirect
npmis-number7.0.0indirect
npmis-plain-object2.0.4indirect
npmis-plain-object5.0.0indirect
npmis-relative1.0.0indirect
npmis-unc-path1.0.0indirect
npmis-valid-glob1.0.0indirect
npmis-windows1.0.2indirect
npmisexe2.0.0indirect
npmisobject3.0.1indirect
npmlast-run2.0.0indirect
npmlead4.0.0indirect
npmliftoff5.0.1indirect
npmmap-cache0.2.2indirect
npmmdn-data2.0.14indirect
npmmicromatch4.0.8indirect
npmmute-stdout2.0.0indirect
npmnormalize-path3.0.0indirect
npmnow-and-later3.0.0indirect
npmobject.defaults1.1.0indirect
npmobject.pick1.3.0indirect
npmonce1.4.0indirect
npmparse-filepath1.0.2indirect
npmparse-passwd1.0.0indirect
npmpath-parse1.0.7indirect
npmpath-root0.1.1indirect
npmpath-root-regex0.1.2indirect
npmpicomatch2.3.1indirect
npmplugin-error1.0.1indirect
npmreadable-stream3.6.2indirect
npmreaddirp3.6.0indirect
npmrechoir0.8.0indirect
npmremove-trailing-separator1.1.0indirect
npmreplace-ext2.0.0indirect
npmreplace-homedir2.0.0indirect
npmrequire-directory2.1.1indirect
npmresolve1.22.10indirect
npmresolve-dir1.0.1indirect
npmresolve-options2.0.0indirect
npmreusify1.1.0indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsemver6.3.1indirect
npmsemver-greatest-satisfied-range2.0.0indirect
npmsource-map0.5.7indirect
npmsource-map0.6.1indirect
npmsparkles2.1.0indirect
npmstream-composer1.0.2indirect
npmstream-exhaust1.0.2indirect
npmstreamx2.22.1indirect
npmstring-width4.2.3indirect
npmstring_decoder1.3.0indirect
npmstrip-ansi6.0.1indirect
npmsupports-color7.2.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmsver1.8.4indirect
npmteex1.0.1indirect
npmtext-decoder1.2.3indirect
npmto-regex-range5.0.1indirect
npmto-through3.0.0indirect
npmunc-path-regex0.1.2indirect
npmundertaker2.0.0indirect
npmundertaker-registry2.0.0indirect
npmutil-deprecate1.0.2indirect
npmv8flags4.0.1indirect
npmvalue-or-function4.0.0indirect
npmvinyl3.0.1indirect
npmvinyl-contents2.0.0indirect
npmvinyl-fs4.0.2indirect
npmvinyl-sourcemap2.0.0indirect
npmvinyl-sourcemaps-apply0.2.1indirect
npmwhich1.3.1indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.9indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 159 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
picomatch2.3.1indirecthigh24.0.4

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