Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-21 08:06 UTC

cliffano / bagofcli

A library for defining CLI commands as JSON configuration

JavaScriptMIT★ 2 stars⑂ 3 forkssince Jun 2013View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

cliffano/bagofcli holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Engineering Quality (74/100) and lowest on Community & Adoption (33/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Cliffano SubagioPersonal account
107 followers120 public repossince May 2009

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 publishTags
npmbagofcli3.1.04,2613030 days agoclicommand-line

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
2.8/36Commit cadence4/52 weeks with commits
14.5/18Commit volume40 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year40
human_commit_share0.97
days_since_last_push4
active_weeks_last_year4
How it's scored
16.2/27Ships releases29 version tags (no GitHub releases)
36/36Release recencylatest release 30 days ago
12.6/27Release cadencea release every ~253.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count29
latest_release_tagv3.1.0
releases_from_tagsyes
days_since_latest_release30
mean_days_between_releases253.6
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?

33At Risk · 17% of overall
How it's scored
0/60Stars2 stars
2.5/25Forks3 forks
0/15Watchers1 watchers
Inputs used
forks3
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, shields.io, snyk.io
has_pull_request_templateno
How it's scored
48.4/80Monthly downloads4,261 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbagofcli
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,261
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.8/22.5Commit distributiontop contributor authored 92% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.922
How it's scored
42/42Issue resolution100% of issues closed
22.5/30PR acceptance6/8 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues0
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs2
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.6/25Owner reach107 followers of cliffano
25/25Track record120 public repos, account ~17 yr old
Inputs used
followers107
owner_typeUser
is_verified
owner_logincliffano
public_repos120
account_age_days6,333
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 30 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbagofcli
ecosystemsnpm
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicscli, nodejs
has_wikiyes
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?

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 7 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
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities17 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages33
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:bagofcli@3.1.0 runtime dependency closure — what installing the published package pulls in — 33 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.

64Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
2.7/40Legible commit history5 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.052
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes20,972
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configeslint.config.js
0/11Static type checking
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
44/55Manageable file sizes1/5 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes70,086
source_files_sampled5
oversized_source_files1
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 examplesexamples
Inputs used
example_dirsexamples
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

2GitHub stars
4contributors
40commits, last 12 months
4days since last push
29releases
1bus factor
0open 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 ★ / 3 ⇿
0Stars
3Forks
8Releases

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.

12233312016-062019-032022-01
Major 2Minor 2Patch 4

Each point covers 6 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-21 08:06 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities17 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
npmasync^3.2.6package.json
npmchalk^6.0.0package.json
npmcommander^15.0.0package.json
npminquirer^14.1.0package.json
npmlodash^4.18.1package.json
npmvalidator^13.15.35package.json
npmyaml-js^0.3.1package.json
All dependencies 145

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

RegistryPackageVersionRelation
npmasync3.2.6direct
npmchalk4.1.2direct
npmchalk6.0.0direct
npmcommander15.0.0direct
npminquirer14.1.0direct
npmlodash4.18.1direct
npmvalidator13.15.35direct
npmyaml-js0.3.1direct
npm@inquirer/ansi2.0.7indirect
npm@inquirer/checkbox5.2.2indirect
npm@inquirer/confirm6.2.0indirect
npm@inquirer/core12.0.0indirect
npm@inquirer/editor5.3.0indirect
npm@inquirer/expand5.1.2indirect
npm@inquirer/external-editor3.0.4indirect
npm@inquirer/figures2.0.8indirect
npm@inquirer/input5.1.3indirect
npm@inquirer/number4.2.0indirect
npm@inquirer/password5.1.2indirect
npm@inquirer/prompts8.6.0indirect
npm@inquirer/rawlist5.3.2indirect
npm@inquirer/search4.3.0indirect
npm@inquirer/select5.2.2indirect
npm@inquirer/type4.0.7indirect
npm@isaacs/cliui8.0.2indirect
npm@pkgjs/parseargs0.11.0indirect
npm@sinonjs/commons3.0.1indirect
npm@sinonjs/fake-timers15.4.0indirect
npm@sinonjs/referee11.0.2indirect
npm@sinonjs/samsam10.0.2indirect
npm@sinonjs/samsam8.0.3indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmavailable-typed-arrays1.0.5indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion2.0.2indirect
npmbrowser-stdout1.3.1indirect
npmcall-bind1.0.2indirect
npmcamelcase6.3.0indirect
npmchardet2.2.0indirect
npmchokidar4.0.3indirect
npmcli-width4.1.0indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcross-spawn7.0.6indirect
npmd1.0.1indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdiff7.0.0indirect
npmdiff9.0.0indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmes5-ext0.10.53indirect
npmes6-iterator2.0.3indirect
npmes6-symbol3.1.3indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmevent-emitter0.3.5indirect
npmext1.6.0indirect
npmfast-string-truncated-width3.0.3indirect
npmfast-string-width3.0.2indirect
npmfast-wrap-ansi0.2.2indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfor-each0.3.3indirect
npmforeground-child3.3.1indirect
npmfunction-bind1.1.1indirect
npmget-caller-file2.0.5indirect
npmget-intrinsic1.2.1indirect
npmglob10.4.5indirect
npmgopd1.0.1indirect
npmhas1.0.3indirect
npmhas-flag4.0.0indirect
npmhas-proto1.0.1indirect
npmhas-symbols1.0.3indirect
npmhas-tostringtag1.0.0indirect
npmhe1.2.0indirect
npmiconv-lite0.7.3indirect
npminherits2.0.4indirect
npmis-arguments1.1.1indirect
npmis-callable1.2.7indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-generator-function1.0.10indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-typed-array1.1.12indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjs-yaml4.1.0indirect
npmlocate-path6.0.0indirect
npmlodash.isarguments3.1.0indirect
npmlog-symbols4.1.0indirect
npmlru-cache10.4.3indirect
npmminimatch9.0.5indirect
npmminipass7.1.2indirect
npmmocha11.8.0indirect
npmms2.1.3indirect
npmmute-stream3.0.0indirect
npmnext-tick1.0.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpicocolors1.1.1indirect
npmrandombytes2.1.0indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmrun-async4.0.6indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmserialize-javascript6.0.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmsinon22.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.2indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtype1.2.0indirect
npmtype2.5.0indirect
npmtype-detect4.0.8indirect
npmtype-detect4.1.0indirect
npmutil0.12.5indirect
npmwhich2.0.2indirect
npmwhich-typed-array1.1.11indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:bagofcli@3.1.0 pulls in 33 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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