Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 17:48 UTC

cisco-open / forge

ForgeMT is a multi-tenant platform for self-hosted GitHub Actions runners on AWS. It gives platform teams an IaC-driven way to operate ephemeral EC2 runners and ARC/Kubernetes runner scale sets for many tenant repositories.

HCL · PythonApache-2.0★ 211 stars⑂ 10 forkssince May 2025View on GitHub ↗
#ci-cd#devops#github-actions#self-hosted-runners#terraform#aws#ephemeral#kubernetes#actions-runner-controller#automation#aws-eks#devsecops#ec2#infrastructure-as-code#multi-tenancy#terragrunt#iam#oidc#open-source#platform-engineering

cisco-open/forge holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Sustainability & Governance (55/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

CiscoOrganization
479 followers121 public repossince Dec 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIforgepoints to another repo — not scored0.22.0-431339 days agodjangosaasforgeframework

Metrics by category

Vitality

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

95Exceptional · 21% of overall

Development activity

92Excellent
How it's scored
36/36Push recency — last push 0 days ago
27.7/36Commit cadence — 40/52 weeks with commits
18/18Commit volume — 508 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_year508
human_commit_share0.45
days_since_last_push0
active_weeks_last_year40

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 85 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~3.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count85
latest_release_tagv4.16.2
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases3.3
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?

68Good · 17% of overall

Popularity & adoption

47Weak
How it's scored
37.7/60Stars — 211 stars
8/25Forks — 10 forks
1.7/15Watchers — 3 watchers
Inputs used
forks10
stars211
watchers3
growth_stateorganic
growth_factor_pct100

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges10
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io, www.bestpractices.dev
has_pull_request_templateyes

Sustainability & Governance

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

55Moderate · 23% of overall

Maintainer resilience (bus factor)

19Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.3/22.5Commit distribution — top contributor authored 99% of commits
4.1/13.5Contributor breadth — 3 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.986

Issue & PR responsiveness

81Excellent
How it's scored
28/42Issue resolution — 67% of issues closed
27.5/30PR acceptance — 633/690 decided PRs merged
10.8/13Newcomer PR acceptance — 5/6 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs633
open_issues7
closed_issues14
prs_merged_7d2
prs_decided_7d3
prs_merged_30d12
prs_decided_30d14
issue_closed_ratio0.667
closed_unmerged_prs57
first_time_authors_30d1
first_time_prs_merged_30d5
first_time_prs_decided_30d6

Ownership & stewardship

72Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
19.3/25Owner reach — 479 followers of cisco-open
22.5/25Track record — 121 public repos, account ~4 yr old
Inputs used
followers479
owner_typeOrganization
is_verifiedno
owner_logincisco-open
public_repos121
account_age_days1,743

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall

Engineering practices

94Exceptional
How it's scored
24/24CI workflows — 16 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 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_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://cisco-open.github.io/forge/
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicsci-cd, devops, github-actions, self-hosted-runners, terraform, aws, ephemeral, kubernetes, actions-runner-controller, automation, aws-eks, devsecops, ec2, infrastructure-as-code, multi-tenancy, terragrunt, iam, oidc, open-source, platform-engineering
has_wikino
homepagehttps://cisco-open.github.io/forge/
docs_sitehttps://cisco-open.github.io/forge/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

81Excellent · 16% of overall

Security posture

93Exceptional
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
1.2/2.5CII-Best-Practices — badge detected: Passing
7.5/7.5Code-Review — all changesets reviewed
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file 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
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate9.3
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

34At Risk
How it's scored
5/35Direct dependencies free of known advisories — 4 affected: black 22.12.0 (critical 9.8), django 4.2.30 (moderate 6.5), pytest 7.4.4 (moderate 6.8), +1 more
8.6/25Indirect dependencies free of known advisories — 1 affected: gunicorn 20.1.0 (high 8.2)
20.5/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 907 days ago
Inputs used
sourceosv
advisories19
affected_packages5
assessed_packages53
unassessed_packages0
affected_by_severitycritical 1, high 1, moderate 3
direct_affected_packages4
Matched the pypi:forge@0.22.0 runtime dependency closure — what installing the published package pulls in — 53 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.

66Good · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 45 of 45 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

77Good
How it's scored
18/18One-command bootstrap — docs/operations/repo-blueprints/containers/containers/action-runner/Makefile, docs/operations/repo-blueprints/containers/containers/pre-commit/Makefile, tests/smoke/Makefile
22/22Automated tests
11/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 35 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesdocs/operations/repo-blueprints/containers/containers/action-runner/Makefile, docs/operations/repo-blueprints/containers/containers/pre-commit/Makefile, tests/smoke/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.35

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — HCL without a type-check config
55/55Manageable file sizes — 0/80 source files over 60KB
Inputs used
primary_languageHCL
largest_source_bytes38,498
source_files_sampled80
oversized_source_files0

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

211GitHub stars
3contributors
508commits, last 12 months
0days since last push
85releases
1bus factor
7open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-16: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 211 stars today.
  • pypi package 'forge' points at a different repository (https://github.com/forgepackages/forge); excluded from ecosystem scoring

More detail

Star and fork history 210 ★ / 10 ⇿
210Stars
10Forks
74Releases

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.

Star history is shown as collected on 2026-07-16. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

0408012016020024021010492025-052025-122026-08
Major 4Minor 33Patch 37

Each point covers 2 days.

OpenSSF Scorecard 9.3 / 10
9.3aggregate

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-12 17:48 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
5CII-Best-Practicesbadge detected: Passing
10Code-Reviewall changesets reviewed
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 127

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

RegistryPackageVersionRelation
PyPIannotated-types0.8.0indirect
PyPIantlr4-python3-runtime4.13.2indirect
PyPIattrs26.1.0indirect
PyPIaws-xray-sdk2.15.0indirect
PyPIbabel2.18.0indirect
PyPIbackrefs8.0indirect
PyPIbandit1.9.4indirect
PyPIblinker1.9.0indirect
PyPIboolean-py5.0indirect
PyPIboto31.35.90indirect
PyPIboto31.43.40indirect
PyPIboto31.43.89indirect
PyPIbotocore1.35.90indirect
PyPIbotocore1.43.40indirect
PyPIbotocore1.43.89indirect
PyPIcachecontrol0.14.4indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcfgv3.5.0indirect
PyPIcfn-lint1.55.1indirect
PyPIcharset-normalizer3.5.1indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.0indirect
PyPIcryptography49.0.0indirect
PyPIcryptography50.0.1indirect
PyPIcyclonedx-python-lib11.12.0indirect
PyPIdefusedxml0.7.1indirect
PyPIdistlib0.4.3indirect
PyPIdocker7.2.0indirect
PyPIfilelock3.32.4indirect
PyPIflask3.1.3indirect
PyPIforge0.0.0indirect
PyPIghp-import2.1.0indirect
PyPIgraphql-core3.2.12indirect
PyPIhypothesis6.167.1indirect
PyPIidentify2.6.19indirect
PyPIidna3.19indirect
PyPIiniconfig2.3.0indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPIjmespath1.1.0indirect
PyPIjoserfc1.7.5indirect
PyPIjsonpatch1.33indirect
PyPIjsonpath-ng1.8.0indirect
PyPIjsonpointer3.1.1indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-path0.5.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIlazy-object-proxy1.12.0indirect
PyPIlicense-expression30.4.4indirect
PyPImarkdown3.10.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.6indirect
PyPImkdocs-material9.7.7indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImoto5.2.2indirect
PyPImoto5.2.3indirect
PyPImpmath1.3.0indirect
PyPImsgpack1.2.2indirect
PyPImultipart2.0.0indirect
PyPInetworkx3.6.1indirect
PyPInodeenv1.10.0indirect
PyPIopenapi-schema-validator0.9.0indirect
PyPIopenapi-spec-validator0.9.0indirect
PyPIpackageurl-python0.17.6indirect
PyPIpackaging26.3indirect
PyPIpaginate0.5.7indirect
PyPIpathable0.6.0indirect
PyPIpathspec1.1.1indirect
PyPIpip26.2.1indirect
PyPIpip-api0.0.34indirect
PyPIpip-audit2.10.1indirect
PyPIpip-requirements-parser32.0.1indirect
PyPIplatformdirs4.11.5indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.2indirect
PyPIpy-partiql-parser0.6.3indirect
PyPIpy-serializable2.1.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.5indirect
PyPIpydantic-core2.46.5indirect
PyPIpydantic-settings2.15.0indirect
PyPIpygments2.21.0indirect
PyPIpyjwt2.13.0indirect
PyPIpymdown-extensions11.0.2indirect
PyPIpyparsing3.3.2indirect
PyPIpytest9.0.3indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.6.0indirect
PyPIpython-dotenv1.2.3indirect
PyPIpywin32312indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIreferencing0.37.0indirect
PyPIregex2026.8.31indirect
PyPIrequests2.34.2indirect
PyPIresponses0.26.1indirect
PyPIresponses0.26.2indirect
PyPIresponses0.26.3indirect
PyPIrfc3339-validator0.1.4indirect
PyPIrich15.0.0indirect
PyPIrpds-py2026.6.3indirect
PyPIs3transfer0.19.2indirect
PyPIsetuptools84.0.0indirect
PyPIsix1.17.0indirect
PyPIsortedcontainers2.4.0indirect
PyPIstevedore5.9.1indirect
PyPIsympy1.14.0indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib32.7.0indirect
PyPIuv0.12.10indirect
PyPIvirtualenv21.7.7indirect
PyPIwatchdog6.0.0indirect
PyPIwerkzeug3.1.8indirect
PyPIwrapt2.4.0indirect
PyPIxmltodict1.0.4indirect
Dependency advisories 5

Installing pypi:forge@0.22.0 pulls in 53 packages, direct and transitive: 5 carry known advisories, of which 4 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
black22.12.0directcritical426.3.1
gunicorn20.1.0indirecthigh422.0.0
django4.2.30directmoderate76.0.8
pytest7.4.4directmoderate29.0.3
python-dotenv0.20.0directmoderate21.2.2

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with cisco-open/forge. Read them side by side →

98bridgecrewio/checkovPrevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.Exceptional98openchoreo/openchoreoOpenChoreo is an internal developer platform for KubernetesExceptional99prowler-cloud/prowlerProwler is the world’s most widely used open-source cloud security platform that automates security and compliance across any cloud environment.Exceptional99argoproj/argo-cdDeclarative Continuous Deployment for KubernetesExceptional98cloud-custodian/cloud-custodianRules engine for cloud security, cost optimization, and governance, DSL in yaml for policies to query, filter, and take actions on resourcesExceptional98pulumi/pulumiPulumi - Infrastructure as Code in any programming language 🚀Exceptional

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 — PyPI.