Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 23:51 UTC

emergent-company / emergent.strategy

GoNo license detected★ 3 stars⑂ 1 forksince Feb 2026View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

emergent-company/emergent.strategy holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (16/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

emergentOrganization
4 followers19 public repossince Jan 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmopencode-epf0.3.0216188 days agoopencodeopencode-pluginepfstrategyproduct-framework

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
27.7/36Commit cadence — 40/52 weeks with commits
18/18Commit volume — 1,118 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,118
human_commit_share1
days_since_last_push7
active_weeks_last_year40
How it's scored
27/27Ships releases — 79 releases published
36/36Release recency — latest release 13 days ago
27/27Release cadence — a release every ~18 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count79
latest_release_tagv0.48.0
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases18

Community & Adoption

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

16Critical · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars3
watchers0
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
17.9/80Monthly downloads — 21 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesopencode-epf
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads21
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.8/22.5Commit distribution — top contributor authored 61% 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.61
How it's scored
28/42Issue resolution — 67% of issues closed
26.2/30PR acceptance — 7/8 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs7
open_issues14
closed_issues28
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.667
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
5/25Owner reach — 4 followers of emergent-company
10.8/25Track record — 19 public repos, account ~0 yr old
Inputs used
followers4
owner_typeOrganization
is_verifiedno
owner_loginemergent-company
public_repos19
account_age_days243
How it's scored
25/25Published & resolvable — 1 package(s) on npm
26/35Publish recency — latest publish 188 days ago
20/20Version history — 6 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesopencode-epf
ecosystemsnpm
any_deprecatedno
min_days_since_publish188

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yaml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

55Moderate
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

31At Risk · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 79 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): CI-Tests. 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, apps/epf-cli/AGENTS.md, apps/epf-cli/internal/embedded/AGENTS.md, apps/strategy-server/AGENTS.md, docs/EPF/AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md, apps/epf-cli/AGENTS.md, apps/epf-cli/internal/embedded/AGENTS.md, apps/strategy-server/AGENTS.md, docs/EPF/AGENTS.md
agent_instruction_max_bytes122,339
How it's scored
18/18One-command bootstrap — apps/epf-cli/Makefile, apps/strategy-server/Taskfile.yml
22/22Automated tests
11/11Lint / format config — .golangci.yaml
11/11Static type checking — packages/opencode-epf/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json, uv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesapps/epf-cli/Makefile, apps/strategy-server/Taskfile.yml
has_devcontainerno
has_linter_configyes
typecheck_configspackages/opencode-epf/tsconfig.json
agent_commit_share0.01
toolchain_manifestsapps/epf-cli/go.mod, apps/orchestrator/go.mod, apps/strategy-server/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
53.1/55Manageable file sizes — 24/713 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes197,036
source_files_sampled713
oversized_source_files24

Key facts

3GitHub stars
4contributors
1,118commits, last 12 months
7days since last push
79releases
1bus factor
14open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch go package 'github.com/emergent-company/emergent-strategy/apps/epf-cli' from its registry
  • Could not fetch go package 'github.com/emergent-company/emergent-strategy/apps/orchestrator' from its registry
  • Could not fetch go package 'github.com/emergent-company/emergent-strategy/apps/strategy-server' from its registry
  • Could not fetch pypi package 'epf-model-compliance' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.1 / 10
3.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-16 23:51 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities79 existing vulnerabilities detected
Direct dependencies 36
RegistryPackageVersion constraintManifest
Gocharm.land/bubbletea/v2v2.0.1apps/epf-cli/go.mod
Gocharm.land/lipgloss/v2v2.0.0apps/epf-cli/go.mod
Gogithub.com/fsnotify/fsnotifyv1.9.0apps/epf-cli/go.mod
Gogithub.com/google/uuidv1.6.0apps/epf-cli/go.mod
Gogithub.com/mark3labs/mcp-gov0.43.2apps/epf-cli/go.mod
Gogithub.com/santhosh-tekuri/jsonschema/v5v5.3.1apps/epf-cli/go.mod
Gogithub.com/spf13/cobrav1.10.1apps/epf-cli/go.mod
Gogithub.com/tliron/commonlogv0.2.21apps/epf-cli/go.mod
Gogithub.com/tliron/glspv0.2.2apps/epf-cli/go.mod
Gogolang.org/x/syncv0.19.0apps/epf-cli/go.mod
Gogopkg.in/yaml.v3v3.0.1apps/epf-cli/go.mod
Gogithub.com/a-h/templv0.3.1020apps/strategy-server/go.mod
Gogithub.com/alexflint/go-argv1.6.1apps/strategy-server/go.mod
Gogithub.com/emergent-company/emergent-strategy/apps/epf-cliv0.0.0-00010101000000-000000000000apps/strategy-server/go.mod
Gogithub.com/emergent-company/go-daisyv0.1.2apps/strategy-server/go.mod
Gogithub.com/golang-jwt/jwt/v5v5.3.1apps/strategy-server/go.mod
Gogithub.com/google/go-github/v68v68.0.0apps/strategy-server/go.mod
Gogithub.com/google/uuidv1.6.0apps/strategy-server/go.mod
Gogithub.com/labstack/echo/v4v4.15.2apps/strategy-server/go.mod
Gogithub.com/mark3labs/mcp-gov0.54.1apps/strategy-server/go.mod
Gogithub.com/pressly/goose/v3v3.27.1apps/strategy-server/go.mod
Gogithub.com/santhosh-tekuri/jsonschema/v6v6.0.2apps/strategy-server/go.mod
Gogithub.com/uptrace/bunv1.2.18apps/strategy-server/go.mod
Gogithub.com/uptrace/bun/dialect/pgdialectv1.2.18apps/strategy-server/go.mod
Gogithub.com/uptrace/bun/driver/pgdriverv1.2.18apps/strategy-server/go.mod
Gogolang.org/x/oauth2v0.36.0apps/strategy-server/go.mod
Gogolang.org/x/textv0.40.0apps/strategy-server/go.mod
Gogopkg.in/yaml.v3v3.0.1apps/strategy-server/go.mod
PyPIanthropic>=0.40.0eval/epf-model-compliance/pyproject.toml
PyPIopenai>=1.50.0eval/epf-model-compliance/pyproject.toml
PyPIgoogle-genai>=1.0.0eval/epf-model-compliance/pyproject.toml
PyPIlangfuse>=2.50.0eval/epf-model-compliance/pyproject.toml
PyPIpydantic>=2.0.0eval/epf-model-compliance/pyproject.toml
PyPIrich>=13.0.0eval/epf-model-compliance/pyproject.toml
PyPIclick>=8.0.0eval/epf-model-compliance/pyproject.toml
PyPIpyyaml>=6.0eval/epf-model-compliance/pyproject.toml
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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.