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

opendefender / OpenRisk

Unified Risk & Threat Intelligence Management Platform

Go · TypeScriptAGPL-3.0★ 14 stars⑂ 1 forksince Oct 2025View on GitHub ↗
KindNetwork serviceWeb interfacehow this is determined

opendefender/OpenRisk holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (89/100) and lowest on Security (48/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

OpenDefenderOrganization
7 followers2 public repossince Nov 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/opendefender/openriskv1.0.7-1150 days ago

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 volume776 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year776
human_commit_share1
days_since_last_push0
active_weeks_last_year26

Release discipline

100Exceptional
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 5 days ago
27/27Release cadencea release every ~37.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tag1.0.8
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases37.2
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?

50Moderate · 17% of overall
How it's scored
18.1/60Stars14 stars
0/25Forks1 forks
1.7/15Watchers3 watchers
Inputs used
forks1
stars14
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
18/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_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

54Moderate · 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
29.6/30PR acceptance138/140 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs138
open_issues0
closed_issues4
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs2
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
6.5/25Owner reach7 followers of opendefender
4.9/25Track record2 public repos, account ~0 yr old
Inputs used
followers7
owner_typeOrganization
is_verified
owner_loginopendefender
public_repos2
account_age_days257
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 150 days ago
4/20Version history1 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/opendefender/openrisk
ecosystemsgo
any_deprecatedno
min_days_since_publish150

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml, eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics19 topics
10/10Wiki
Inputs used
topicsanalysis, cybersecurity, digital-forensics, digital-forensics-analysis, freesoftware, incidence-response-plan, observable, obsevability, python, security-tools, cyber-threat-intelligenece, grc, opendefender, openrisk, risk-analysis, risk-assessment, risk-management, risks, risks-score
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

48Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/8 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
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities73 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.8
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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, docs/Claude.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 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_filesCLAUDE.md, docs/Claude.md
agent_instruction_max_bytes130,116
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.golangci.yml, eslint.config.js
11/11Static type checkingfrontend/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice33 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsfrontend/tsconfig.json
agent_commit_share0.33
toolchain_manifestsagent/go.mod, backend/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
54.9/55Manageable file sizes2/825 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes109,967
source_files_sampled825
oversized_source_files2
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)docs/openapi.yaml
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesdocs/openapi.yaml
interfaces_expected_ofnetwork-service

Key facts

14GitHub stars
1contributors
776commits, last 12 months
0days since last push
8releases
1bus factor
0open issues
Go, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch go package 'github.com/opendefender/openrisk-agent' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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 00:10 UTC

9Binary-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
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/8 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities73 existing vulnerabilities detected
Direct dependencies 65
RegistryPackageVersion constraintManifest
Gocloud.google.com/go/computev1.64.0backend/go.mod
Gogithub.com/Azure/azure-sdk-for-go/sdk/azcorev1.22.0backend/go.mod
Gogithub.com/Azure/azure-sdk-for-go/sdk/azidentityv1.14.0backend/go.mod
Gogithub.com/Azure/azure-sdk-for-go/sdk/resourcemanager/resourcegraph/armresourcegraphv0.10.0backend/go.mod
Gogithub.com/anthropics/anthropic-sdk-gov1.56.0backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2v1.42.1backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/configv1.32.30backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/credentialsv1.19.29backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/service/ec2v1.316.1backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/service/s3v1.105.1backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/service/securityhubv1.73.1backend/go.mod
Gogithub.com/docker/dockerv28.5.2+incompatiblebackend/go.mod
Gogithub.com/go-ldap/ldap/v3v3.4.14backend/go.mod
Gogithub.com/go-pdf/fpdfv0.9.0backend/go.mod
Gogithub.com/go-playground/validator/v10v10.28.0backend/go.mod
Gogithub.com/gofiber/fiber/v2v2.52.12backend/go.mod
Gogithub.com/golang-jwt/jwt/v5v5.3.1backend/go.mod
Gogithub.com/golang-migrate/migrate/v4v4.19.1backend/go.mod
Gogithub.com/google/go-github/v66v66.0.0backend/go.mod
Gogithub.com/google/uuidv1.6.0backend/go.mod
Gogithub.com/lib/pqv1.10.9backend/go.mod
Gogithub.com/pquerna/otpv1.5.0backend/go.mod
Gogithub.com/prometheus/client_golangv1.19.0backend/go.mod
Gogithub.com/redis/go-redis/v9v9.6.3backend/go.mod
Gogithub.com/rs/zerologv1.35.0backend/go.mod
Gogithub.com/skip2/go-qrcodev0.0.0-20200617195104-da1b6568686ebackend/go.mod
Gogithub.com/stretchr/testifyv1.11.1backend/go.mod
Gogithub.com/vmware/govmomiv0.55.1backend/go.mod
Gogitlab.com/gitlab-org/api/client-gov1.46.0backend/go.mod
Gogolang.org/x/cryptov0.54.0backend/go.mod
Gogolang.org/x/oauth2v0.36.0backend/go.mod
Gogoogle.golang.org/apiv0.288.0backend/go.mod
Gogorm.io/datatypesv1.2.7backend/go.mod
Gogorm.io/driver/postgresv1.6.0backend/go.mod
Gogorm.io/driver/sqlitev1.6.0backend/go.mod
Gogorm.io/gormv1.31.1backend/go.mod
Gok8s.io/apiv0.34.2backend/go.mod
Gok8s.io/apimachineryv0.34.2backend/go.mod
Gok8s.io/client-gov0.34.2backend/go.mod
npm@hello-pangea/dnd^18.0.1frontend/package.json
npm@hookform/resolvers^5.2.2frontend/package.json
npm@tanstack/react-query^5.0.0frontend/package.json
npmaxios^1.13.2frontend/package.json
npmclsx^2.1.1frontend/package.json
npmdate-fns^4.1.0frontend/package.json
npmframer-motion^12.23.24frontend/package.json
npmleaflet^1.9.4frontend/package.json
npmlodash^4.17.21frontend/package.json
npmlucide-react^0.554.0frontend/package.json
npmreact^19.2.0frontend/package.json
npmreact-circular-progressbar^2.2.0frontend/package.json
npmreact-confetti^6.4.0frontend/package.json
npmreact-dom^19.2.0frontend/package.json
npmreact-grid-layout^1.5.2frontend/package.json
npmreact-hook-form^7.66.1frontend/package.json
npmreact-hot-toast^2.6.0frontend/package.json
npmreact-leaflet^5.0.0frontend/package.json
npmreact-router-dom^7.9.6frontend/package.json
npmreact-use^17.6.0frontend/package.json
npmrecharts^3.5.0frontend/package.json
npmsonner^2.0.7frontend/package.json
npmtailwind-merge^3.4.0frontend/package.json
npmuse-sound^5.0.0frontend/package.json
npmzod^4.1.12frontend/package.json
npmzustand^5.0.8frontend/package.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 statisticsGo.