Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 14:25 UTC

OmarEhab007 / RemedyIQ

Cloud-native log analysis platform for BMC Remedy AR Server — Go backend, Next.js dashboard, ClickHouse analytics, and Claude AI-powered insights

Go · TypeScriptMIT★ 1 star⑂ 0 forkssince Feb 2026View on GitHub ↗
KindNetwork serviceWeb interfacehow this is determined

OmarEhab007/RemedyIQ holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (80/100) and lowest on Community & Adoption (24/100). It was last updated 113 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Omar EhabPersonal account
67 followers39 public repossince Dec 2019

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 publish
Gogithub.com/OmarEhab007/RemedyIQv0.6.0-6180 days ago

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 113 days ago
3.5/36Commit cadence5/52 weeks with commits
16/18Commit volume60 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year60
human_commit_share1
days_since_last_push113
active_weeks_last_year5
How it's scored
27/27Ships releases1 releases published
27/36Release recencylatest release 180 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv0.6.0
releases_from_tagsno
days_since_latest_release180
mean_days_between_releases
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?

24At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 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
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
40.4/42Issue resolution96% of issues closed
30/30PR acceptance25/25 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs25
open_issues1
closed_issues25
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.962
closed_unmerged_prs0
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
13.2/25Owner reach67 followers of OmarEhab007
23.7/25Track record39 public repos, account ~6 yr old
Inputs used
followers67
owner_typeUser
is_verified
owner_loginOmarEhab007
public_repos39
account_age_days2,436
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 go
35/35Publish recencylatest publish 180 days ago
20/20Version history6 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/OmarEhab007/RemedyIQ
ecosystemsgo
any_deprecatedno
min_days_since_publish180

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests11 out of 18 merged PRs checked by a CI test -- score normalized to 6
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/10Topics17 topics
10/10Wiki
Inputs used
topicsbmc-remedy, golang, logging, ai, claude, clickhouse, dashboard, devops, docker, log-analysis, nats, nextjs, observability, react, redis, saas, typescript
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?

32At Risk · 16% of overall
How it's scored
5.2/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.5/2.5CI-Tests11 out of 18 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/28 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
3.5/5SASTSAST tool detected but not run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities173 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history55 of 60 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.917
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes8,681
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingfrontend/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice33 of the last 60 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.55
toolchain_manifestsbackend/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
54.7/55Manageable file sizes2/341 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes61,567
source_files_sampled341
oversized_source_files2
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)docs/api/openapi.yaml, specs/001-remedyiq-mvp/contracts/openapi.yaml, specs/003-enhanced-analysis-dashboard/contracts/openapi.yaml, specs/006-fix-dashboard-data/contracts/openapi.yaml, specs/007-complete-log-explorer/contracts/openapi.yaml, specs/008-trace-transaction/contracts/openapi.yaml, specs/012-analyzer-insights/contracts/openapi.yaml
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesdocs/api/openapi.yaml, specs/001-remedyiq-mvp/contracts/openapi.yaml, specs/003-enhanced-analysis-dashboard/contracts/openapi.yaml, specs/006-fix-dashboard-data/contracts/openapi.yaml, specs/007-complete-log-explorer/contracts/openapi.yaml, specs/008-trace-transaction/contracts/openapi.yaml, specs/012-analyzer-insights/contracts/openapi.yaml
interfaces_expected_ofnetwork-service

Key facts

1GitHub stars
1contributors
60commits, last 12 months
113days since last push
1releases
1bus factor
1open issues
Go, 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

More detail

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-08-13 14:25 UTC

7Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests11 out of 18 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/28 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
7SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities173 existing vulnerabilities detected
Direct dependencies 39
RegistryPackageVersion constraintManifest
Gogithub.com/ClickHouse/clickhouse-go/v2v2.43.0backend/go.mod
Gogithub.com/anthropics/anthropic-sdk-gov1.22.0backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2v1.41.1backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/credentialsv1.19.7backend/go.mod
Gogithub.com/aws/aws-sdk-go-v2/service/s3v1.96.0backend/go.mod
Gogithub.com/blevesearch/bleve/v2v2.5.7backend/go.mod
Gogithub.com/google/uuidv1.6.0backend/go.mod
Gogithub.com/gorilla/muxv1.8.1backend/go.mod
Gogithub.com/gorilla/websocketv1.5.3backend/go.mod
Gogithub.com/jackc/pgx/v5v5.9.0backend/go.mod
Gogithub.com/joho/godotenvv1.5.1backend/go.mod
Gogithub.com/nats-io/nats.gov1.48.0backend/go.mod
Gogithub.com/redis/go-redis/v9v9.17.3backend/go.mod
Gogithub.com/stretchr/testifyv1.11.1backend/go.mod
Gogoogle.golang.org/genaiv1.46.0backend/go.mod
npm@clerk/nextjs^6.39.2frontend/package.json
npm@radix-ui/react-slot^1.2.4frontend/package.json
npm@tanstack/react-query^5.62.0frontend/package.json
npmclass-variance-authority^0.7.1frontend/package.json
npmclsx^2.1.1frontend/package.json
npmcmdk^1.1.1frontend/package.json
npmd3-array^3.2.4frontend/package.json
npmd3-scale^4.0.2frontend/package.json
npmdompurify^3.4.0frontend/package.json
npmlucide-react^0.563.0frontend/package.json
npmnext16.2.4frontend/package.json
npmprism-react-renderer^2.4.1frontend/package.json
npmradix-ui^1.4.3frontend/package.json
npmreact^19.2.4frontend/package.json
npmreact-dom^19.2.4frontend/package.json
npmreact-window^1.8.10frontend/package.json
npmrecharts^3.7.0frontend/package.json
npmsonner^2.0.0frontend/package.json
npmstreamdown^2.2.0frontend/package.json
npmtailwind-merge^3.4.0frontend/package.json
npmzustand^5.0.0frontend/package.json
npm@clerk/nextjs^6.37.3package.json
npmreact-window^2.2.6package.json
npmrecharts^3.7.0package.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.31.0 — full methodology · metrics wiki.

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