Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-23 07:40 UTC

jayminwest / seeds

Git-native issue tracker for AI agent workflows. Zero dependencies, JSONL storage, Bun runtime.

TypeScriptMIT★ 111 stars⑂ 26 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

jayminwest/seeds holds a health index of 78 out of 100, placing it in the Good band. It scores highest on AI Readiness (90/100) and lowest on Security (49/100). It was last updated 5 days ago. 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)
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).

Ownership

Jaymin WestPersonal account
515 followers77 public repossince May 2017jayminwest.com

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
npm@os-eco/seeds-cli0.5.153,342305 days agoissue-trackinggitaiagentsclideveloper-tools

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
10.4/36Commit cadence15/52 weeks with commits
18/18Commit volume384 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_year384
human_commit_share1
days_since_last_push5
active_weeks_last_year15

Release discipline

100Exceptional
How it's scored
27/27Ships releases29 releases published
36/36Release recencylatest release 5 days ago
27/27Release cadencea release every ~5.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count29
latest_release_tagv0.5.15
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases5.5
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?

60Moderate · 17% of overall
How it's scored
33.1/60Stars111 stars
11.7/25Forks26 forks
0/15Watchers1 watchers
Inputs used
forks26
stars111
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
47/80Monthly downloads3,342 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@os-eco/seeds-cli
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,342
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
27.3/30PR acceptance90/99 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/27 approved changesets -- score normalized to 0
Inputs used
merged_prs90
open_issues0
closed_issues3
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs9
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
19.5/25Owner reach515 followers of jayminwest
25/25Track record77 public repos, account ~9 yr old
Inputs used
followers515
owner_typeUser
is_verified
owner_loginjayminwest
public_repos77
account_age_days3,367
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 5 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@os-eco/seeds-cli
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.eslintrc, .eslintrc.cjs, .eslintrc.js, .eslintrc.yml, biome.json, eslint.config.js, eslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

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

49Weak · 16% of overall
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests17 out of 17 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/27 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

90Excellent · 4% of overall
How it's scored
45/45Agent instructions.bun/install/cache/bun-types@1.3.9@@@1/CLAUDE.md, .bun/install/cache/undici@7.25.0@@@1/docs/docs/api/Agent.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.99
agent_instruction_files.bun/install/cache/bun-types@1.3.9@@@1/CLAUDE.md, .bun/install/cache/undici@7.25.0@@@1/docs/docs/api/Agent.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes23,936
How it's scored
18/18One-command bootstrap.bun/install/cache/retry@0.12.0@@@1/Makefile
22/22Automated tests
11/11Lint / format config.eslintrc, .eslintrc.cjs, .eslintrc.js, .eslintrc.yml, biome.json, eslint.config.js, eslint.config.mjs
11/11Static type checking.bun/install/cache/@anthropic-ai/sdk@0.91.1@@@1/src/tsconfig.json, .bun/install/cache/@aws-crypto/crc32@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/sha256-browser@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/sha256-js@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/supports-web-crypto@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/util@5.2.0@@@1/tsconfig.json, .bun/install/cache/ast-types@0.13.4@@@1/tsconfig.json, .bun/install/cache/fast-uri@3.1.2@@@1/tsconfig.json, .bun/install/cache/openai@6.26.0@@@1/src/tsconfig.json, .bun/install/cache/protobufjs@7.5.8@@@1/tsconfig.json, tsconfig.json
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
10/10Demonstrated agent practice16 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files.bun/install/cache/retry@0.12.0@@@1/Makefile
has_devcontaineryes
has_linter_configyes
typecheck_configs.bun/install/cache/@anthropic-ai/sdk@0.91.1@@@1/src/tsconfig.json, .bun/install/cache/@aws-crypto/crc32@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/sha256-browser@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/sha256-js@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/supports-web-crypto@5.2.0@@@1/tsconfig.json, .bun/install/cache/@aws-crypto/util@5.2.0@@@1/tsconfig.json, .bun/install/cache/ast-types@0.13.4@@@1/tsconfig.json, .bun/install/cache/fast-uri@3.1.2@@@1/tsconfig.json, .bun/install/cache/openai@6.26.0@@@1/src/tsconfig.json, .bun/install/cache/protobufjs@7.5.8@@@1/tsconfig.json, tsconfig.json
agent_commit_share0.16
toolchain_manifests.bun/install/cache/@mariozechner/clipboard@0.3.5@@@1/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.5/55Manageable file sizes92/9,463 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes9,144,216
source_files_sampled9,463
oversized_source_files92
How it's scored
40/40API schema (OpenAPI/GraphQL/proto).bun/install/cache/protobufjs@7.5.8@@@1/google/api/annotations.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/api/http.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/api.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/descriptor.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/source_context.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/type.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample, examples
Inputs used
example_dirsexample, examples
has_mcp_signalno
api_schema_files.bun/install/cache/protobufjs@7.5.8@@@1/google/api/annotations.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/api/http.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/api.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/descriptor.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/source_context.proto, .bun/install/cache/protobufjs@7.5.8@@@1/google/protobuf/type.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

111GitHub stars
1contributors
384commits, last 12 months
5days 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
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index npm:@os-eco/seeds-cli@0.5.15; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 26 ⇿
0Stars
26Forks
28Releases

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.

0510152025302632026-022026-052026-07
Major 0Minor 4Patch 24
OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-07-23 07:40 UTC

0Binary-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
10CI-Tests17 out of 17 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/27 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmajv^8package.json
npmchalk^5.6.2package.json
npmcommander^14.0.3package.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

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.