Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 20:05 UTC

marcusrbrown / systematic

Structured engineering workflows for OpenCode

TypeScriptMIT★ 23 stars⑂ 2 forkssince Jan 2026View on GitHub ↗

marcusrbrown/systematic holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (92/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Marcus R. BrownPersonal account
174 followers111 public repossince Jun 2011

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@fro.bot/systematic2.33.34,7881441 day agoopencodepluginaiworkflowengineering

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
18/36Commit cadence26/52 weeks with commits
18/18Commit volume575 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year575
human_commit_share
days_since_last_push0
active_weeks_last_year26

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~4.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv2.33.3
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases4.1
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?

47Weak · 17% of overall
How it's scored
21.8/60Stars23 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars23
watchers0
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
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
49.1/80Monthly downloads4,788 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@fro.bot/systematic
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,788
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.7/22.5Commit distributiontop contributor authored 57% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.57
How it's scored
37.8/42Issue resolution90% of issues closed
29.6/30PR acceptance591/600 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/30 approved changesets -- score normalized to 1
Inputs used
merged_prs591
open_issues3
closed_issues27
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.9
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
16.1/25Owner reach174 followers of marcusrbrown
25/25Track record111 public repos, account ~15 yr old
Inputs used
followers174
owner_typeUser
is_verified
owner_loginmarcusrbrown
public_repos111
account_age_days5,518
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 1 days ago
20/20Version history144 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@fro.bot/systematic
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://fro.bot/systematic
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsai, bun, opencode, plugin, semantic-release, systematic, workflow
has_wikino
homepagehttps://fro.bot/systematic
docs_sitehttps://fro.bot/systematic
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 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.8/7.5Code-ReviewFound 4/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 5 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 18 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities60 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

92Excellent · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, AGENTS.md, docs/AGENTS.md, registry/files/profiles/omo/AGENTS.md, registry/files/profiles/standalone/AGENTS.md, src/lib/AGENTS.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, docs/AGENTS.md, registry/files/profiles/omo/AGENTS.md, registry/files/profiles/standalone/AGENTS.md, src/lib/AGENTS.md
agent_instruction_max_bytes8,423
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapmise.toml
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingdocs/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configyes
typecheck_configsdocs/tsconfig.json, tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
53.7/55Manageable file sizes2/84 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes108,265
source_files_sampled84
oversized_source_files2
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

23GitHub stars
4contributors
575commits, last 12 months
0days since last push
100releases
1bus factor
3open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 7.0 / 10
7.0aggregate

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-15 20:05 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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/30 approved changesets -- score normalized to 1
10Contributorsproject has 5 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 18 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities60 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
npm@astrojs/starlight^0.39.0docs/package.json
npmastro^6.4.2docs/package.json
npmrehype-mermaid^3.0.0docs/package.json
npmsharp^0.34.0docs/package.json
npmjs-yaml^4.1.1package.json
npmjsonc-parser^3.3.0package.json
npmzod4.4.3package.json
All dependencies 37

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

RegistryPackageVersionRelation
npm@astrojs/starlight^0.39.0direct
npmastro^6.4.2direct
npmjs-yaml^4.1.1direct
npmjsonc-parser^3.3.0direct
npmrehype-mermaid^3.0.0direct
npmsharp^0.34.0direct
npmzod4.1.8direct
npmzod4.4.3direct
npm@biomejs/biome2.5.3indirect
npm@opencode-ai/plugin1.17.18indirect
npm@opencode-ai/plugin1.3.15indirect
npm@opencode-ai/sdk1.17.18indirect
npm@opencode-ai/sdk1.3.15indirect
npm@semantic-release/exec7.1.0indirect
npm@types/bunlatestindirect
npm@types/js-yaml4.0.9indirect
npm@types/node24.13.3indirect
npmajv8.20.0indirect
npmajv-formats3.0.1indirect
npmconventional-changelog-conventionalcommits9.3.1indirect
npmcross-spawn7.0.6indirect
npmexpress^4.19.2indirect
npmexpress-session^1.18.0indirect
npmisexe2.0.0indirect
npmmarkdownlint-cli0.48.0indirect
npmpath-key3.1.1indirect
npmpg^8.11.5indirect
npmplaywright1.61.1indirect
npmrimraf6.1.3indirect
npmsemantic-release25.0.6indirect
npmsemantic-release-export-data1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmtypescript6.0.3indirect
npmwhich2.0.2indirect
PyPIgoogle-genaiindirect
PyPIpillowindirect
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.11.0 — full methodology · metrics wiki.

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