Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 05:49 UTC

remkop / picocli

Picocli is a modern framework for building powerful, user-friendly, GraalVM-enabled command line apps with ease. It supports colors, autocompletion, subcommands, and more. In 1 source file so apps can include as source & avoid adding a dependency. Written in Java, usable from Groovy, Kotlin, Scala, etc.

JavaApache-2.0★ 5,416 stars⑂ 480 forkssince Feb 2017View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

remkop/picocli holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (81/100) and lowest on Vitality (51/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Remko PopmaPersonal account
302 followers32 public repossince Nov 2013

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Maveninfo.picocli:picocli4.7.7-86496 days ago

Metrics by category

Vitality

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

51Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 11 days ago
6.2/36Commit cadence9/52 weeks with commits
12.2/18Commit volume22 commits in the last year
2/10OpenSSF Scorecard: Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year22
human_commit_share0.69
days_since_last_push11
active_weeks_last_year9
How it's scored
27/27Ships releases86 releases published
7.2/36Release recencylatest release 496 days ago
12.6/27Release cadencea release every ~140.1 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count86
latest_release_tagv4.7.7
releases_from_tagsno
days_since_latest_release496
mean_days_between_releases140.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

81Excellent · 17% of overall
How it's scored
60/60Stars5,416 stars
22.3/25Forks480 forks
9/15Watchers43 watchers
Inputs used
forks480
stars5,416
watchers43
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.5/22.5Commit distributiontop contributor authored 85% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 44 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.846
How it's scored
38.2/42Issue resolution91% of issues closed
21.6/30PR acceptance623/865 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 10/21 approved changesets -- score normalized to 4
Inputs used
merged_prs623
open_issues142
closed_issues1,421
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.909
closed_unmerged_prs242
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.8/25Owner reach302 followers of remkop
23.1/25Track record32 public repos, account ~12 yr old
Inputs used
followers302
owner_typeUser
is_verified
owner_loginremkop
public_repos32
account_age_days4,671
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on maven
14/35Publish recencylatest publish 496 days ago
20/20Version history86 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesinfo.picocli:picocli
ecosystemsmaven
any_deprecatedno
min_days_since_publish496

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests4 out of 10 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://picocli.info
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicsjava, commandline, parser, ansi-colors, annotations, ansi, subcommands, cli, cli-framework, git, autocomplete, completion, bash-completion, options-parsing, command-line-parser, argument-parsing, command-line, graalvm, native-image, executable
has_wikiyes
homepagehttps://picocli.info
docs_sitehttps://picocli.info
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
4.5/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
1/2.5CI-Tests4 out of 10 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 10/21 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 44 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
3.5/5SASTSAST tool detected but not run on all commits
2/5Security-Policysecurity policy file detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages9
unassessed_packages0
affected_by_severitynone
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 9 resolved dependencies against OSV. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.6/40Legible commit history24 of 69 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.348
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapbuild.gradle, picocli-codegen-tests-java9plus/build.gradle, picocli-codegen/build.gradle (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingJava (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance31 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsbuild.gradle, picocli-codegen-tests-java9plus/build.gradle, picocli-codegen/build.gradle, picocli-examples/annotation-processing/example-gradle-project-kotlin-graal-nativeimage/build.gradle, picocli-examples/annotation-processing/example-gradle-project/build.gradle, picocli-examples/annotation-processing/example-maven-project-shading/pom.xml, picocli-examples/annotation-processing/example-maven-project-simple/pom.xml, picocli-examples/build.gradle, picocli-examples/generate-man-pages/example-gradle-project/build.gradle, picocli-examples/generate-man-pages/example-maven-project/pom.xml, picocli-groovy/build.gradle, picocli-shell-jline2/build.gradle, picocli-shell-jline3/build.gradle, picocli-spring-boot-starter/build.gradle, picocli-tests-java567/build.gradle, picocli-tests-java8/build.gradle, picocli-tests-java9plus/build.gradle, picocli-tests-jpms-modules/app-it/build.gradle, picocli-tests-jpms-modules/app/build.gradle, picocli-tests-jpms-modules/build.gradle, pom.xml
dependency_bot_commit_share0.31
How it's scored
45/45Type-checkable codeJava (statically typed)
52.7/55Manageable file sizes19/460 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes1,241,375
source_files_sampled460
oversized_source_files19
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample, examples, sample
Inputs used
example_dirsexample, examples, sample
has_mcp_signalno
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

5,416GitHub stars
99contributors
22commits, last 12 months
11days since last push
86releases
1bus factor
142open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 480 ⇿
0Stars
480Forks
79Releases

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.

010020030040050047292017-052022-012026-08
Major 4Minor 19Patch 43

Each point covers 9 days.

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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-08-28 05:49 UTC

6Binary-Artifactsbinaries present in source code
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
4CI-Tests4 out of 10 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/21 approved changesets -- score normalized to 4
10Contributorsproject has 44 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
7SASTSAST tool detected but not run on all commits
4Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 9

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

RegistryPackageVersionRelation
Maveninfo.picocli:picocli4.7.7indirect
Maveninfo.picocli:picocli-codegen4.7.7indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.7.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.8.1indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin2.2indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin3.2.0indirect
Mavenorg.apache.maven.plugins:maven-shade-plugin1.4indirect
Mavenorg.asciidoctor:asciidoctor-maven-plugin2.1.0indirect
Mavenorg.codehaus.mojo:exec-maven-plugin3.0.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 9 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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.

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